Interface with user-defined match monad?
if there's a match in scope, we use this as the match strategy, assuming it conforms to MatchStrategy as defined below:
The phase defined by this transform
A standard phase template
Represent a match as a formula in propositional logic that encodes whether the match matches (abstractly: we only consider types)
The global environment; overridden by instantiation in Global.
The global environment; overridden by instantiation in Global.
List of phase names, this phase should run after
List of phase names, this phase should run after
Phase name this phase will attach itself to, not allowing any phase to come between it and the phase name declared
Phase name this phase will attach itself to, not allowing any phase to come between it and the phase name declared
SubComponent are added to a HashSet and two phases are the same if they have the same name
SubComponent are added to a HashSet and two phases are the same if they have the same name
Internal flag to tell external from internal phases
Internal flag to tell external from internal phases
Create a new phase which applies transformer
Create a new phase which applies transformer
The transformer factory
The transformer factory
The phase corresponding to this subcomponent in the current compiler run
The phase corresponding to this subcomponent in the current compiler run
The name of the phase
The name of the phase
New flags defined by the phase which are not valid before
New flags defined by the phase which are not valid before
New flags defined by the phase which are not valid until immediately after it
New flags defined by the phase which are not valid until immediately after it
List of phase names, this phase should run before
List of phase names, this phase should run before
(patternMatching: StringAdd).self
(patternMatching: StringFormat).self
(patternMatching: ArrowAssoc[PatternMatching]).x
(Since version 2.10.0) Use leftOfArrow instead
(patternMatching: Ensuring[PatternMatching]).x
(Since version 2.10.0) Use resultOfEnsuring instead
Translate pattern matching.
Either into optimized if/then/else's, or virtualized as method calls (these methods form a zero-plus monad), similar in spirit to how for-comprehensions are compiled.
For each case, express all patterns as extractor calls, guards as 0-ary extractors, and sequence them using
flatMap(lifting the body of the case into the monad usingone).Cases are combined into a pattern match using the
orElsecombinator (the implicit failure case is expressed using the monad'szero).TODO:
(longer-term) TODO: