Packages

  • package root
    Definition Classes
    root
  • package info
    Definition Classes
    root
  • package kwarc
    Definition Classes
    info
  • package mmt
    Definition Classes
    kwarc
  • package api

    This is the main package of the MMT API.

    This is the main package of the MMT API.

    It holds subpackages for all data structures, data containers, and the central algorithms and services.

    Classes directly defined in the package

    Some minor classes that are used throughout MMT are defined in this package, in particular:

    • MMT URIs in the class Path and Namespace
    • processing and content errors in the class Error

    The package also contains root classes for certain types that are subclassed throughout the package. Most importantly:

    • StructuralElement: structure-level (= named) parts in the data structures for the MMT language: documents, theories, constants, ...
    • MMTTask: tasks for a single object: parsing, checking, ...
    • Rule: object-level part of the MMT language that is written in Scala

    Subpackages

    Data structures for the MMT language

    The data structures for the MMT languages are defined in 4 packages corresponding to the 4 levels: - documents: Documents and all other NarrativeElements - modules: Modules (= the toplevel declarations), in particular Theorys and Views - symbols: all Declarations inside modules, in particular Constants - objects: all anonymous Objects (e.g., formulas, functions, etc.), in particular Contexts and Terms

    The former 3 levels are jointly called 'structural' levels. All elements subclass StructuralElement, have an MMT URI, and carry an MMT URI referring to their parent in the MMT abstract syntax tree.

    Structural elements are extensible (via DerivedModules and DerivedDeclarations), and the package patterns defines declaration patterns as a built-in extension.

    All structural elements are mutable and implement the ContainerElement interface for changing their children. Objects, by contrast, are represented as immutable inductive types.(except for carrying metadata.Metadata and objects.ClientProperties). The boundary between structural elements and objects is mediated by ComponentContainers: these are mutable, owned by structural elements, and maintain objects.

    A few auxiliary data structures shifted to separate packages: - opaque: external (i.e., informal, computation) content - informal: partially outdated informal data structures - metadata: metadata annotations to all structural elements or objects

    The MMT main class and its internal state

    The package frontend contains the class Controller, which owns all state relevant for running MMT. Typically, each application creates a single instance of this class. The package also defines several other essential classes, most importantly MMT's extension (=plug-in, add-on) interfaces via the Extension class.

    The package libraries maintains the instances of MMT language data structures, in particular the Library class. Controller owns a Library, which stores all structural elements that have been loaded into memory.

    User interfaces

    The package frontend also contains the main executable classes, in particular the Shell class.

    The package gui collects all classes for building graphical user interfaces. This includes auxiliary classes for use in IDE plugins.

    The package web collects all classes for the HTTP interface of MMT.

    Physical storage of the MMT language files

    The package archives defines MMT Archives (= projects) as well as classes for building and working with archives. The latter include in particular the BuildManager and BuildTarget. Build targets include Importers and [Exporter]]s that translate between MMT and other formats.

    The package backend defines classes for maintaining archives and translating between the MMT URIs of structural elements and their physical storage locations.

    The central algorithms for processing MMT content

    The processing model of MMT consists of several major algorithms. - parser: read strings into MMT data structures - checking: check and refine MMT data structures - uom: pure computation on MMT data structures - proving: theorem proving on MMT data structures (in very early state)) - execution: imperative computation (in very, very early state) - presentation: rendering MMT data structures in user-facing formats (including HTML+presentation MathML)

    All algorithms are defined in Extensions coupled with default implementations. Moreover, all algorithms are split into two separate levels, one for structural elements and objects. See LeveledExtension.

    The package notations maintains the common code for parsing and presentation.

    The package valuebases maintains mathematical databases as a part of MMT.

    Other algorithms on the MMT data structures

    The package ontology contains a relational, semantic web-style ontology and query engine for it.

    The package moc contains change management.

    The package refactoring contains refactoring principles.

    General purpose utility functions

    The package utils defines general purpose APIs for files, URIs, HTML building, etc.

    Definition Classes
    mmt
  • package archives

    This package holds all classes related to MMT Archives (= project).

    This package holds all classes related to MMT Archives (= project).

    The BuildManager allows defining BuildTargets to run on archives, including in particular Importers and Exporters.

    Most archives are stored in hub of git repositories such as and MathHub or GitHub. Such hubs are represented by the class LMHHub, which allows for cloning, etc. archives.

    The list of currently open archives (from which MMT will load content if needed) is maintained by the backend.Backend.

    Definition Classes
    api
  • package backend

    This package maintains the interface between MMT content in persistent physical storage and MMT content loaded into memory.

    This package maintains the interface between MMT content in persistent physical storage and MMT content loaded into memory.

    The class Storage is the interface for individual physical storage containers. Most of the time this corresponds to a folder containing an archives.Archive.

    Content is usually stored in OMDoc XML format, which is parsed by the XMLStreamer.

    The class Backend maintains the registered storages and performs conversion between logical MMT URIs and physical locations.

    The frontend.Controller owns an instance of Backend. Any referenced MMT URI is lazily and transparently loaded from the backend into memory and unloaded if MMT runs out of memory.

    Definition Classes
    api
  • package checking

    The algorithm for checking MMT content.

    The algorithm for checking MMT content. See api for an overview of the algorithms.

    The main interfaces are - Checker: the main interface for checkers (combining a structure and an object checker) - StructureChecker: checking structural elements - ObjectChecker: checking objects

    The main implementations are - MMTStructureChecker for structural elements - RuleBasedChecker for objects

    The latter creates a Solver for each judgment, which perform type reconstruction.

    Structure checking is not extensible except through DerivedElements. Object checking is extensible through Rules.

    Definition Classes
    api
  • package documents

    NarrativeElements are all elements that do not have a semantics of their own.

    NarrativeElements are all elements that do not have a semantics of their own.

    The most important case are Documents. Inside, documents a few other other documents may occur.

    Definition Classes
    api
  • package execution

    The algorithm for imperatively executing MMT content.

    The algorithm for imperatively executing MMT content. This is currently very young and immature.

    See api for an overview of the algorithms.

    Definition Classes
    api
  • package frontend

    This package defines several central classes: - Controller is the main MMT class.

    This package defines several central classes: - Controller is the main MMT class. - Shell is the main executable (which will create one controller). - MMTConfig is the MMT configuration data structure. A controller maintains one configuration. - Extension is the addon/plugin interface of MMT. Every extension has access to one controller instance. - Report handles logging, and every instance of Logger has access to a report instance.

    Definition Classes
    api
  • package gui

    GUIPanel and [GUIFrame]] maintain a swing-based graphical interface to the frontend.Controller and its children.

    GUIPanel and [GUIFrame]] maintain a swing-based graphical interface to the frontend.Controller and its children.

    Definition Classes
    api
  • package informal
    Definition Classes
    api
  • package libraries

    Library maintains the structural elements that have been loaded into memory.

    Library maintains the structural elements that have been loaded into memory. That includes the theory diagram and all documents.

    ImplicitGraph maintains the commutative sub-diagram of implicit morphisms.

    Definition Classes
    api
  • package metadata

    MetaDatum is the stateless class that represents metadata items.

    MetaDatum is the stateless class that represents metadata items.

    MetaData statefully maintains a set of MetaDatums.

    Elements that have metadata inherit from HasMetaData.

    Linker and Tagger make setting and getting metadata easier.

    Definition Classes
    api
  • package moc

    Change is the main class statelessly representing differences/changes.

    Change is the main class statelessly representing differences/changes.

    Differ is a differ for MMT data structures.

    Definition Classes
    api
  • package modules

    MMT Modules, i.e., Theorys and Views.

    MMT Modules, i.e., Theorys and Views.

    Link unifies Views and symbols.Structures, the two kinds of atomic theory morphisms.

    ModuleOrLink unifies the two. That class defines most of the state of a module, in particular the body.

    Definition Classes
    api
  • package notations

    This package maintains the common data structures for parsing and presentation.

    This package maintains the common data structures for parsing and presentation.

    TextNotation is the main notation class. It is similar to MMT objects, in particular it is stateless.

    NotationContainer statefully maintains the notations assigned to a declaration. These are owned by StructuralElements to carry notations, akin to how they carry type/definition.

    Definition Classes
    api
  • package objects

    MMT objects are

    MMT objects are

    AnonymousDiagram, AnonymousTheory, and AnonymousMorphism represent anonymous counterparts to libraries.Library modules.Module}.

    This package also contains various auxiliary classes: - Position defines paths within objects - SubstitutionApplier is the main interface for substitution strategies. - Matcher is a simple matcher.

    Definition Classes
    api
  • package ontology

    This package contains a relational ontology and a query engine for it.

    This package contains a relational ontology and a query engine for it.

    The main classes are: - RelationalElement defines the concepts and relation of the ontology (TBox) - RelationalManager extracts the ABox from MMT content - RelStore maintains the model of the ontology (ABox) - RelationGraphExporter allows exporting the ABox as a graph. - Query defines a query language for the ontology - Evaluator implements the query language for a given ABox. - Search maintains classes for faceted search, in particular the facet for MathWebSearch.

    Definition Classes
    api
  • package opaque

    Informal or unknown content that MMT does not process.

    Informal or unknown content that MMT does not process. The main classes are - OpaqueElement: such content - OpaqueElementInterpreter the abstract interface for extensions that interpret it

    Definition Classes
    api
  • package parser

    The algorithm for parsing MMT content (strings to MMT data structures).

    The algorithm for parsing MMT content (strings to MMT data structures). See api for an overview of the algorithms.

    The main interfaces are - Parser: the main interface for parser (combining a structure and an object parser) - StructureParser: parsing structural elements - ObjectParser: parsing objects

    The main implementations are - KeywordBasedParser for structural elements in .mmt files - NotationBasedParser for objects

    The latter creates a Scanner for each string, which applies notations to parse user-defined mixifx syntax.

    Structure parsing is extensible using ParserExtensions. Object parsing is extensible using notations or LexerExtensions.

    Definition Classes
    api
  • package patterns

    Declaration patterns in the sense of Horozal's PhD thesis, realized as two special cases of structural features: - Pattern for the patterns (elaborates to nothing) - Instance for the instances of patterns (elaborates by looking up the pattern)

    Declaration patterns in the sense of Horozal's PhD thesis, realized as two special cases of structural features: - Pattern for the patterns (elaborates to nothing) - Instance for the instances of patterns (elaborates by looking up the pattern)

    Definition Classes
    api
  • package presentation

    The algorithm for presenting MMT content (data structures to user-facing formats).

    The algorithm for presenting MMT content (data structures to user-facing formats). See api for an overview of the algorithms.

    The main interfaces are - Presenter: the main interface for parser (combining a structure and an object parser) - StructurePresenter: presenting structural elements - ObjectPresenter: presenting objects

    The main implementations are (in each case for structural elements and objects) - for OMDoc XML: OMDocPresenter resp. OpenMathPresenter - for plain strings (using the toString methods): TextPresenter resp. ObjectTextPresenter - for nice human-oriented strings: MMTStructurePresenter resp. NotationBasedParser - for HTML: HTMLPresenter resp. MathMLPresenter

    Definition Classes
    api
  • package proving

    The algorithm for proving theorems about MMT content.

    The algorithm for proving theorems about MMT content. This is very premature and experimental.

    See api for an overview of the algorithms.

    The main interfaces are - Prover: object level proving

    Structure level proving does not exist yet.

    The main implementations are - RuleBasedProver for object-level proving

    The latter creates a Searcher for each proving task, which applies search rules to find MMT objects.

    Definition Classes
    api
  • package refactoring
    Definition Classes
    api
  • package symbols

    MMT Declarations are the elements of Modules.

    MMT Declarations are the elements of Modules. The kinds of declarations are documented at Declaration.

    ObjContainer are owned by structural elements, in particular by declarations, to store objects.

    Definition Classes
    api
  • ApplyMorphism
  • ApplyMorphismLazy
  • ApplySubs
  • BoundTheoryParameters
  • Constant
  • ConstantAssignment
  • ContextContainer
  • Declaration
  • DefLinkAssignment
  • DerivedContentElement
  • DerivedDeclaration
  • DerivedModule
  • Elaboration
  • FinalConstant
  • GeneralStructuralFeature
  • GenerativePushout
  • HasDefiniens
  • HasNotation
  • HasType
  • IdentityInclude
  • IdentityTranslator
  • Include
  • IncludeData
  • IncludeLike
  • LazyConstant
  • LinkInclude
  • ModuleLevelFeature
  • NestedModule
  • OMLReplacer
  • OMSReplacer
  • ObjContainer
  • ObjDimension
  • ParametricTheoryLike
  • PlainInclude
  • Renamer
  • RuleConstant
  • RuleConstantInterpreter
  • RuleConstantParser
  • SimpleDeclaredStructure
  • SimpleLazyConstant
  • SimpleStructure
  • StructuralFeature
  • StructuralFeatureRule
  • StructuralFeatureUtil
  • Structure
  • TermContainer
  • TheoryLike
  • Translator
  • TraversingTranslator
  • TypedConstantLike
  • TypedParametricTheoryLike
  • UniformTranslator
  • UnnamedUntyped
  • Untyped
  • Visibility
  • package uom

    The algorithm for immutably computing with MMT content, i.e., simplification (strings to MMT data structures).

    Simplification

    The algorithm for immutably computing with MMT content, i.e., simplification (strings to MMT data structures). See api for an overview of the algorithms.

    The main interfaces are - Simplifier: the main interface for parser (combining a structure and an object simplifier) - StructureSimplifier: simplifying structural elements - ObjectSimplifier: simplifying objects

    The main implementations are - ElaborationBasedSimplifier for structural elements - RuleBasedSimplifier for objects

    Structure simplification is extensible using derived elements. Object simplification is extensible using rules.

    Literals and semantic objects

    This package also contains the classes for using Scala objects as MMT literals.

    SemanticType defines types as sets of Scala objects. SemanticValue defines a distinguished element of such a type. SemanitcOperator defines functions on such types as Scala functions.

    Literals and operations on them are injected into the MMT language by declaring RealizedValue, RealizedType and RealizedOperator rules, which tie a syntactic type/operator (i.e., an MMT term) to a semantic counterpart.

    StandardLiterals defines semantic types for the most important types.

    RealizedTheory represents an MMT theory programmed in Scala, usually as a Scala class.

    Scala companion objects for MMT theories

    TheoryScala and ConstantScala are auxiliary classes that are useful when implementing MMT rules or other logic-specific algorithms.

    Definition Classes
    api
  • package utils

    This package defines various MMT-independent high-level APIs.

    This package defines various MMT-independent high-level APIs. Various basic functions are declared directly in this package object in order to be easily available.

    Most other files in this package are self-contained and independent of the rest of MMT and each other. We describe them in groups below.

    Data structures*

    - Union disjoint union of Scala types - MyList extensions of Scala's lists (via implicit conversions) - HashRelation, HashMapToSet, and HashEquality: hash-related data structures for - While while loops that allow for break and continue

    General purpose utilities

    - Killable tasks that can be notified that they should be canceled. In particular, MMTTasks can be aborted without risking an inconsistent state. - Unparsed for simple parsing of strings - ScalaTo serialization helpers for Scala objects - ValueCache factory methods that introduce structure sharing by resuing previous pointers - XMLToScala framework for conveniently turning a set of case classes into an XML parser for the corresponding schema

    Wrappers for low-level APIs

    MMT provides various APIs that extend or simplify APIs provided Java or Scala: - File file paths and interacting with files - URI URIs - xml various helper function for working with XML and dereferencing URLs (not really a wrapper but fits best here) - ShellCommand commands executed on the system shell

    APIs for external languages

    - Dot the dot languages for graph layouting - JSON the JSON language - HTML API for building HTML pages programmatically

    Definition Classes
    api
  • package valuebases

    This package maintains databases of cocnrete mathematical objects.

    This package maintains databases of cocnrete mathematical objects.

    Concrete objects are special MMT Terms that can be represented as concrete database objects (e.g., JSON). The connection between the two is mediated by Codecs and CodecOerator. The codec-based translation is implemented in the Coder.

    Definition Classes
    api
  • package web

    Server maintains the HTTP interface of MMT.

    Server maintains the HTTP interface of MMT. The server is owned by the frontend.Controller.

    It can be customized by ServerExtensions.

    The REPLServer maintains a set of independent REPL loops for MMT content.

    Definition Classes
    api
p

info.kwarc.mmt.api

symbols

package symbols

MMT Declarations are the elements of Modules. The kinds of declarations are documented at Declaration.

ObjContainer are owned by structural elements, in particular by declarations, to store objects.

Source
package.scala
Linear Supertypes
Ordering
  1. Alphabetic
  2. By Inheritance
Inherited
  1. symbols
  2. AnyRef
  3. Any
  1. Hide All
  2. Show All
Visibility
  1. Public
  2. All

Type Members

  1. case class ApplyMorphism(lup: Lookup, morph: Term) extends UniformTranslator with Product with Serializable

    a translator that applies a morphism (lazily)

  2. case class ApplyMorphismLazy(morph: Term) extends UniformTranslator with Product with Serializable

    a translator that applies a morphism (lazily)

  3. case class ApplySubs(subs: Substitution) extends UniformTranslator with Product with Serializable

    a translator that performs substitution

  4. class BoundTheoryParameters extends StructuralFeature with IncludeLike
  5. abstract class Constant extends Declaration with HasType with HasDefiniens with HasNotation

    the abstract interface to MMT constants with a few basic methods

  6. class ContextContainer extends ObjContainer[Context]

    container for mutable contexts

  7. abstract class Declaration extends ContentElement

    Declarations are the children of Modules.

    Declarations are the children of Modules.

    They are mostly Constants for the syntax and RuleConstants for the semantics (= rule-based implementation). The MMT data model is extensible via DerivedDeclarations.

    Structures (except for includes) are conceptually a derived declaration but are hard-coded as a separate kind of declaration. Inlcudes are represented as special cases of structures.

  8. trait DerivedContentElement extends AbstractTheory with HasType with HasNotation

    A DerivedContentElement unifies feature of Constant and Theory but without a commitment to the semantics.

    A DerivedContentElement unifies feature of Constant and Theory but without a commitment to the semantics. The semantics is defined by the corresponding StructuralFeature

  9. class DerivedDeclaration extends Declaration with DerivedContentElement

    a declarations that is elaborated into more primitive declarations

  10. class DerivedModule extends Module with DerivedContentElement

    a module that is elaborated into more primitive module

  11. abstract class Elaboration extends ElementContainer[Declaration]

    the return type of elaborating a DerivedDeclaration by a StructuralFeature

  12. class FinalConstant extends Constant

    the main class for a concrete MMT constant

  13. abstract class GeneralStructuralFeature[Level <: DerivedContentElement] extends FormatBasedExtension

    A StructureFeature defines the semantics of a DerivedDeclaration

    A StructureFeature defines the semantics of a DerivedDeclaration

    The semantics consists of a set of declarations that are injected into the parent theory after the DerivedDeclaration These are called the 'outer declarations'.

    All methods that take a dd:DerivedDeclaration can assume - dd.feature == this.feature - dd.getComponents has the same components as this.expectedComponents and in the same order

  14. class GenerativePushout extends StructuralFeature with IncludeLike

    Generative, definitional functors/pushouts with free instantiation called structures in original MMT

  15. trait HasDefiniens extends AnyRef
  16. trait HasNotation extends AnyRef

    declarations that have a notation

  17. trait HasType extends AnyRef
  18. case class IncludeData(home: Term, from: MPath, args: List[Term], df: Option[Term], total: Boolean) extends Product with Serializable

    Auxiliary class that collects information about a structure that acts like an include.

    Auxiliary class that collects information about a structure that acts like an include.

    home

    The module in which this include is declared (e.g. a theory T, view V, etc.)

    from

    The domain D of the included theory (into T, or into domain of V)

    args

    Instantiations of the parameters of from (if any, e.g. for parametric theories)

    df

    Definiens (of type D(args) -> T, or D(args) -> codomain of V)

    total

    A total include is one that must be implemented by the containing theory this becomes available as a morphism only at the end of the containing theory (even if there is a definiens, which can happen, e.g., if the definiens refers to other total includes) invariants: if df contains mor then args.isEmpty && from is domain of df else OMPMOD(from,args) is included theory Note that concrete syntax may allow "include df" because D because can be infered; in a theory, "include D" is the standard for includes without definiens; in a view, we may also allow "include D" for the case where df is the identity of D. See the examples below!

    Examples:
    1. A Theory T includes a theory S in the usual way: theory S : ?someMetaTheory = ... ❚ theory T : ?someMetaTheory = include ?S ❙ ❚ Both theories are non-parametric, i.e. as usual. Then T.getAllIncludes will contain an IncludeData(T.path, S.path, Nil, None, false).

    2. ,
    3. Assume S, T as above, as well as a View v: T -> R including another view w: S -> R: view w : S -> R = ... ❚ view v : T -> R = include ?S ❘ = ?w ❙ ❚ Then v.getAllIncludes will contain an IncludeData(v.path, S.path, Nil, w.path, false).

    4. ,
    5. Let R, S, T be as below: theory R : ?someMetaTheory = ... ❚ theory S : ?someMetaTheory = include ?R❙ ... ❚ theory T : ?someMetaTheory = include ?R ❙ ... ❚ Pictorially, this is an inclusion triangle (with one missing edge): R / \ T S Now suppose we want a View v: T -> S which is the identity on R, i.e. v_R = id_R. In surface syntax we can do this as follows: view v: T -> S = include ?R❙ ❚ With this v.getAllIncludes will contain an IncludeData(v.path, R.path, Nil, Some(OMIDENT(R.path)), false).

    6. ,
    7. If you have a View v: T -> S between two theories with the same meta theory mt, then v.getAllIncludes will automatically include IncludeData(v.path, mt.path, Nil, Some(OMIDENT(mt.path)), false) similar to the previous example where the view is the identity on the included theory.

    See also

    https://uniformal.github.io//doc/language/implicit.html

  19. trait IncludeLike extends AnyRef

    for structural features with unnamed declarations whose type is an instance of a named theory

  20. abstract class LazyConstant extends Constant

    a Constant whose fields are computed on demand

  21. abstract class ModuleLevelFeature extends GeneralStructuralFeature[DerivedModule]
  22. class NestedModule extends Declaration with ModuleWrapper

    a Module as a Declaration, i.e., inside some other module

  23. class OMLReplacer extends StatelessTraverser

    replaces all naked OML's; for convenience a substitution is used even though we are replacing OML's not OMV's

  24. abstract class OMSReplacer extends StatelessTraverser

    A traverser to replace references to GlobalNames by a custom term given by the abstract method OMSReplacer.replace.

  25. trait ObjContainer[T <: Obj] extends AbstractObjectContainer

    TermContainer acts as the interface between the structural and the object level

    TermContainer acts as the interface between the structural and the object level

    Elements like info.kwarc.mmt.api.symbols.Constant that have a info.kwarc.mmt.api.objects.Term as a component will not declare a term directly but a TermContainer.

    TermContainer keeps track of different syntactic representations of the same semantic term. It also stores additional status information.

    The representations are read < parsed < analyzed < normalized. Setting a representation marks the higher representations as dirty.

    T

    the type of objects stored; the type bound is not actually needed, but it helps putting sharper bound on some return types

  26. class ObjDimension[T] extends AnyRef

    a mutable wrapper around a value together with status information

  27. trait ParametricTheoryLike extends StructuralFeature

    for structural features that are parametric theories with special meaning, e.g., patterns, inductive types

  28. class Renamer extends OMSReplacer

    a translator that renames local names of a module

  29. class RuleConstant extends Declaration

    A RuleConstant is a declaration whose value is an externally provided rule.

    A RuleConstant is a declaration whose value is an externally provided rule. Its inner structure is not representable in or accessible to MMT, but it exposes functionality that MMT can use and that defines the semantics of MMT.

  30. class RuleConstantInterpreter extends AnyRef

    loads a rule (by reflection) given by a LocalName corresponding to a java name of a Rule object or of a StructuralFeature class

  31. class RuleConstantParser extends ParserExtension
  32. abstract class SimpleLazyConstant extends LazyConstant
  33. abstract class StructuralFeature extends GeneralStructuralFeature[DerivedDeclaration]
  34. case class StructuralFeatureRule(cls: Class[_ <: StructuralFeature], feature: String) extends Rule with Product with Serializable

    a rule that legitimizes a StructuralFeature

  35. class Structure extends Declaration with Link with HasType

    MMT structures, given by a body and an optional definiens

  36. class TermContainer extends ObjContainer[Term] with AbstractTermContainer

    container for mutable terms

  37. trait TheoryLike extends StructuralFeature
  38. abstract class Translator extends AnyRef

    a general purpose term translator

    a general purpose term translator

    There are a number of desirable properties that Translator can have. In particular: preservation of typing, equality; commute with substitution.

  39. abstract class TraversingTranslator extends UniformTranslator

    a translator obtained from a traverser

  40. trait TypedConstantLike extends AnyRef
  41. trait TypedParametricTheoryLike extends StructuralFeature with ParametricTheoryLike

    for structural features that take both parameters and a type Examples are structural features which build structures defined via a derived declaration of another structural feature like inductively-defined functions or proofs by induction over an inductively-defined type or terms of a record In such a case the type is the other derived declaration instantiated with values for its parameters

  42. abstract class UniformTranslator extends Translator

    a translator that maps all terms in the same way (i.e., applyDef and applyType are the same)

  43. trait UnnamedUntyped extends AnyRef
  44. trait Untyped extends AnyRef
  45. case class Visibility(tp: Boolean, _df: Boolean) extends Product with Serializable

    visibility information for a Constant

    visibility information for a Constant

    tp

    type is visible

    _df

    definiens is visible (must be invisible if type is)

Value Members

  1. object Constant

    helper object

  2. object ConstantAssignment

    An MMT assignment to a constant is a special case of a Constant.

  3. object ContextContainer
  4. object DefLinkAssignment

    An MMT assignment to a definitional link is a special case of a DefinedStructure.

  5. object Elaboration
  6. object IdentityInclude

    a LinkInclude of the identity morphism: the analog to a plain include in a theory

  7. object IdentityTranslator extends UniformTranslator

    identity (non-traversing)

  8. object Include

    unnamed imports with automatic sharing are represented as special Structures

    unnamed imports with automatic sharing are represented as special Structures

    they do not carry assignments their name is LocalName(from)

  9. object LinkInclude

    include of a morphism into a link

  10. object OMLReplacer
  11. object OMSReplacer
  12. object ParametricTheoryLike

    helper object

  13. object PlainInclude

    A PlainInclude represents an MMT inclusion between theories.

  14. object Renamer
  15. object RuleConstant
  16. object SimpleDeclaredStructure

    apply/unapply functions for SimpleDeclaredStructures whose domain is an MPath

  17. object SimpleStructure

    this can be wrapped around a pattern for matching a structure, e.g., case SimpleStructure(s, fromPath)

  18. object StructuralFeatureUtil
  19. object Structure

    auxiliary functions

  20. object TermContainer

    helper object

  21. object TraversingTranslator
  22. object TypedParametricTheoryLike

    helper object

  23. object Visibility extends Serializable

Inherited from AnyRef

Inherited from Any

Ungrouped