Add @scala.annotation.preview annotation and -preview flag.
#22317
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
So what happens when a library uses a preview feature and publishes? A user can depend on it without turning on preview? |
Yes, user can depend on it without turning on preview as long as the exposed API does not use any preview features. Preview features can become an implementation detail that is not exposed to referrer of definition. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds
@scala.annotation.previewand-previewflag to enable definition and usage of experimental-like features.@previewfeatures follows the same rules as@experimentalwith exception of being non viral - we're not automatically adding@previewannotation to when refering to preview definitions, but still require preview scope (by either-previewflag or top levelscala.language.preview.<feature>)