ccConfig
Members list
Value members
Concrete methods
If true, use "sealed" as encapsulation mechanism, meaning that we check that type variable instantiations don't have cap in any of their capture sets. This is an alternative of the original restriction that cap can't be boxed or unboxed. It is dropped in 3.5 but used again in 3.6.
If true, use "sealed" as encapsulation mechanism, meaning that we check that type variable instantiations don't have cap in any of their capture sets. This is an alternative of the original restriction that cap can't be boxed or unboxed. It is dropped in 3.5 but used again in 3.6.
Attributes
Concrete fields
If true, allow mapping capture set variables under captureChecking with maps that are neither bijective nor idempotent. We currently do now know how to do this correctly in all cases, though.
If true, allow mapping capture set variables under captureChecking with maps that are neither bijective nor idempotent. We currently do now know how to do this correctly in all cases, though.
Attributes
Don't require @use for reach capabilities that are accessed only in a nested closure. This is unsound without additional mitigation measures, as shown by unsound-reach-5.scala.
Don't require @use for reach capabilities that are accessed only in a nested closure. This is unsound without additional mitigation measures, as shown by unsound-reach-5.scala.
Attributes
If enabled, use a special path in recheckClosure for closures that are eta expansions. This can improve some error messages.
If enabled, use a special path in recheckClosure for closures that are eta expansions. This can improve some error messages.