-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change @experimental spec #13305
Change @experimental spec #13305
Conversation
b73376c
to
c4edfde
Compare
fb8bfc1
to
d08b595
Compare
311c290
to
8f43d17
Compare
8f43d17
to
1828dc1
Compare
* As this definition is in `src-non-bootstrapped`, it will not be published. | ||
* It may accidentally be visible while compiling the non-bootstrapped library. | ||
*/ | ||
@experimental def testExperimental = 4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure how important it is to test this given that @experimental
is no longer experimental itself now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not really there to check if @experimental
is experimental, it is to check that we can define experimental definitions in the standard library. This is to make sure we catch a regression as early as possible as this kind of failure could block an update if the reference compiler.
Note that for 3.1.0
we will not have any other experimental definitions. They will all get stabilized.
Co-authored-by: Guillaume Martres <[email protected]>
The main differences with the current version is that @experimental is not experimental and that we are able to define experimental APIs using any version of the compiler (nightly, snapshot and stable release).
See
docs/docs/reference/experimental/experimental-defs.md
.