PostTyper
Related Doc:
package transform
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.
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.
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.
Output should be checkable by TreeChecker
Output should be checkable by TreeChecker
Is this phase the standard typerphase? True for FrontEnd, but not for other first phases (such as FromTasty).
Is this phase the standard typerphase? True for FrontEnd, but not for other first phases (such as FromTasty). The predicate is tested in some places that perform checks and corrections. It's different from isAfterTyper (and cheaper to test).
The last phase during which the transformed denotations are valid
The last phase during which the transformed denotations are valid
the following two members override abstract members in Transform
If set, allow missing or superfluous arguments in applications and type applications.
If set, allow missing or superfluous arguments in applications and type applications.
List of names of phases that should precede this phase
List of names of phases that should precede this phase
The transformation method
The transformation method
The phase in which the transformation should be run.
The phase in which the transformation should be run. By default this is the phase given by the this macro transformer, but it could be overridden to be the phase following that one.
Throws an UnsupportedOperationException with the given method name.
Throws an UnsupportedOperationException with the given method name.
The validity period of the transformer in the given context
The validity period of the transformer in the given context
A macro transform that runs immediately after typer and that performs the following functions:
(1) Add super accessors and protected accessors (@see SuperAccessors)
(2) Convert parameter fields that have the same name as a corresponding public parameter field in a superclass to a forwarder to the superclass field (corresponding = super class field is initialized with subclass field) (@see ForwardParamAccessors)
(3) Add synthetic methods (@see SyntheticMethods)
(4) Check that
Newnodes can be instantiated, and that annotations are valid(5) Convert all trees representing types to TypeTrees.
(6) Check the bounds of AppliedTypeTrees
(7) Insert
.packagefor selections of package object members(8) Replaces self references by name with
this(9) Adds SourceFile annotations to all top-level classes and objects
(10) Adds Child annotations to all sealed classes
(11) Minimizes
callfields ofInlinenodes to just point to the toplevel class from which code was inlined.The reason for making this a macro transform is that some functions (in particular super and protected accessors and instantiation checks) are naturally top-down and don't lend themselves to the bottom-up approach of a mini phase. The other two functions (forwarding param accessors and synthetic methods) only apply to templates and fit mini-phase or subfunction of a macro phase equally well. But taken by themselves they do not warrant their own group of miniphases before pickling.