CheckCaptures

The typechecker pass

Check overrides again, taking capture sets into account. TODO: Can we avoid doing overrides checks twice? We need to do them here since only at this phase CaptureTypes are relevant But maybe we can then elide the check during the RefChecks phase under captureChecking?

A name given to the Phase that can be used to debug the compiler. For instance, it is possible to print trees after a given phase using:

$ ./bin/scalac -Xprint:<phaseNameHere> sourceFile.scala

Change any ResetPrivate flags back to Private

If set, implicit search is enabled

Can this transform change the base types of a type?

Can this transform create or delete non-private members?

Can this transform change the parents of a class?

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. -1 if the phase is not installed in the context.

Output should be checkable by TreeChecker

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).

The last phase during which the transformed denotations are valid

If set, allow missing or superfluous arguments in applications and type applications.

List of names of phases that should precede this phase

Show tree with rechecked types instead of the types stored in the .tpe field

Returns a string representation of the object.

The default representation is platform dependent.

The transformation method

The validity period of the transformed denotations in the given context