This phase eliminates ExprTypes => T as types of method parameter references, and replaces them b
nullary function types. More precisely:
For the types of parameter symbols:
=> T ==> () => T
For cbn parameter values
x ==> x()
Note: This scheme to have inconsistent types between method types (whose formal types are still ExprTypes and parameter valdefs (which are now FunctionTypes) is not pretty. There are two other options which have been abandoned or not yet pursued.
Option 1: Transform => T to () => T also in method and function types. The problem with this is that is that it requires to look at every type, and this forces too much, causing Cyclic Reference errors. Abandoned for this reason.
Option 2: Merge ElimByName with erasure, or have it run immediately before. This has not been tried yet.
- Companion
- object
Value members
Concrete methods
Inherited methods
Can this transform change the base types of a type?
Can this transform change the base types of a type?
- Inherited from
- Phase
Can this transform create or delete non-private members?
Can this transform create or delete non-private members?
- Inherited from
- Phase
Check what the phase achieves, to be called at any point after it is finished.
Check what the phase achieves, to be called at any point after it is finished.
- Inherited from
- Phase
If denotation had an ExprType before, it now gets a function type
If denotation had an ExprType before, it now gets a function type
- Inherited from
- TransformByNameApply
The sequence position of this phase in the given context where 0 is reserved for NoPhase and the first real phase is at position 1. -1 if the phase is not installed in the context.
The sequence position of this phase in the given context where 0 is reserved for NoPhase and the first real phase is at position 1. -1 if the phase is not installed in the context.
- Inherited from
- Phase
Output should be checkable by TreeChecker
Output should be checkable by TreeChecker
- Inherited from
- Phase
Is this phase the standard typerphase? True for TyperPhase, but not for other first phases (such as FromTasty or Parser). The predicate is tested in some places that perform checks and corrections. It's different from ctx.isAfterTyper (and cheaper to test).
Is this phase the standard typerphase? True for TyperPhase, but not for other first phases (such as FromTasty or Parser). The predicate is tested in some places that perform checks and corrections. It's different from ctx.isAfterTyper (and cheaper to test).
- Inherited from
- Phase
The last phase during which the transformed denotations are valid
The last phase during which the transformed denotations are valid
- Inherited from
- DenotTransformer
If set, use relaxed typing for all phases in group
If set, use relaxed typing for all phases in group
- Inherited from
- MiniPhase
List of names of phases that should precede this phase
List of names of phases that should precede this phase
- Inherited from
- Phase
List of names of phases that should have finished their processing of all compilation units before this phase starts
List of names of phases that should have finished their processing of all compilation units before this phase starts
- Inherited from
- MiniPhase
Transform tree using all transforms of current group (including this one)
Transform tree using all transforms of current group (including this one)
- Inherited from
- MiniPhase
Transform single node using all transforms following the current one in this group
Transform single node using all transforms following the current one in this group
- Inherited from
- MiniPhase
Transform tree using all transforms following the current one in this group
Transform tree using all transforms following the current one in this group
- Inherited from
- MiniPhase
The validity period of the transformed denotations in the given context
The validity period of the transformed denotations in the given context
- Inherited from
- DenotTransformer