scala.language.experimental
The experimental object contains features that are known to have unstable API or behavior that may change in future releases.
Experimental features may undergo API changes in future releases, so production code should not rely on them.
Programmers are encouraged to try out experimental features and report any bugs or API inconsistencies they encounter so they can be improved in future releases.
AttributesExperimental support for capture checking; implies support for pureFunctions
Experimental support for capture checking; implies support for pureFunctions
AttributesExperimental support for erased modifier
Experimental support for erased modifier
Experimental support for generic number literals.
Experimental support for generic number literals.
AttributesExperimental support for automatic conversions of arguments, without requiring a language import import scala.language.implicitConversions.
Experimental support for automatic conversions of arguments, without requiring a language import import scala.language.implicitConversions.
Experimental support for new features for better modularity, including
Experimental support for new features for better modularity, including
Experimental support for named type arguments.
Experimental support for named type arguments.
AttributesExperimental support for package object values
Experimental support for package object values
AttributesExperimental support for pure function type syntax
Experimental support for pure function type syntax
AttributesExperimental support for quote pattern matching with polymorphic functions
Experimental support for quote pattern matching with polymorphic functions
AttributesExperimental support for typechecked exception capabilities
Experimental support for typechecked exception capabilities
AttributesExperimental support for improvements in for comprehensions
Experimental support for improvements in for comprehensions
[Since version 3.7] The `experimental.betterFors` language import no longer has any effect, the feature is being stablised and can be enabled using `-preview` flag
Enhance match type extractors to follow aliases and singletons.
Enhance match type extractors to follow aliases and singletons.
Attributes[Since version 3.6] The experimental.betterMatchTypeExtractors language import is no longer needed since the feature is now standard. It now has no effect, including when setting an older source version.
Adds support for clause interleaving: Methods can now have as many type clauses as they like, this allows to have type bounds depend on terms: def f(x: Int)[A <: x.type]: A
Adds support for clause interleaving: Methods can now have as many type clauses as they like, this allows to have type bounds depend on terms: def f(x: Int)[A <: x.type]: A
[Since version 3.6] `clauseInterleaving` is now standard, no language import is needed
Experimental support for using indentation for arguments
Experimental support for using indentation for arguments
Attributes[Since version 3.3] `fewerBraces` is now standard, no language import is needed
Experimental support for named tuples.
Experimental support for named tuples.
Attributes[Since version 3.7] The experimental.namedTuples language import is no longer needed since the feature is now standard
Was needed to add support for relaxed imports of extension methods. The language import is no longer needed as this is now a standard feature since SIP was accepted.
Was needed to add support for relaxed imports of extension methods. The language import is no longer needed as this is now a standard feature since SIP was accepted.
Attributes[Since version 3.4] The experimental.relaxedExtensionImports language import is no longer needed since the feature is now standard
Only where this feature is enabled, are macro definitions allowed.
Only where this feature is enabled, are macro definitions allowed. If macros is not enabled, macro definitions are rejected by the compiler.
Macro implementations and macro applications are not governed by this language feature; they can be used anywhere.
Why introduce the feature? Macros promise to make the language more regular, replacing ad-hoc language constructs with a general powerful abstraction capability that can express them. Macros are also a more disciplined and powerful replacement for compiler plugins.
Why control it? For their very power, macros can lead to code that is hard to debug and understand.
AttributesRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4