Skip to content

Correctly check experimental features #12672

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

Merged
merged 1 commit into from
Jun 2, 2021

Conversation

anatoliykmetyuk
Copy link
Contributor

@anatoliykmetyuk anatoliykmetyuk commented Jun 1, 2021

  • When inlining: emit "experimental" error only when
    the feature in question is actually annotated as
    experimental
  • Compiler-wide: treat non-bootstrapped compiler as
    experimental-friendly. The motivation is to compile
    the standard library with experimental features enabled
    at all times. This change isn't supposed to introduce any
    experimental features leaks into stable builds since
    we do not publish non-bootstrapped compiler.

This is supposed to fix the 3.0.1-RC1 release which failed due to broken experimental feature checks: https://github.com/lampepfl/dotty/runs/2717422630?check_suite_focus=true

- When inlining: emit "experimental" error only when
  the feature in question is actually annotated as
  experimental
- Compiler-wide: treat non-bootstrapped compiler as
  experimental-friendly. The motivation is to compile
  the standard library with experimental features enabled
  at all times. This change isn't supposed to introduce any
  experimental features leaks into stable builds since
  we do not publish non-bootstrapped compiler.
@nicolasstucki nicolasstucki merged commit 8df379e into scala:master Jun 2, 2021
@nicolasstucki nicolasstucki deleted the experimental-stdlib branch June 2, 2021 05:46
anatoliykmetyuk pushed a commit that referenced this pull request Jun 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants