Collect fields that can be nulled out after use in lazy initialization.
This information is used during lazy val transformation to assign null to private fields that are only used within a lazy val initializer. This is not just an optimization, but is needed for correctness to prevent memory leaks. E.g.
class TestByNameLazy(byNameMsg: => String) {
lazy val byLazyValMsg = byNameMsg
}
Here byNameMsg should be null out once byLazyValMsg is
initialised.
A field is nullable if all the conditions below hold:
- belongs to a non trait-class
- is private[this]
- is not lazy
- its type is nullable after erasure
- is only used in a lazy val initializer
- defined in the same class as the lazy val
- Companion
- object
Value members
Concrete methods
Map lazy values to the fields they should null after initialization.
Map lazy values to the fields they should null after initialization.
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
Can this transform change the parents of a class?
Can this transform change the parents of a class?
- 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
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 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 ctx.isAfterTyper (and cheaper to test).
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 ctx.isAfterTyper (and cheaper to test).
- Inherited from
- Phase
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 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