Skip to content
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

Scala 3 experimental features should be more clearly labeled as experimental #2976

Open
SethTisue opened this issue Feb 16, 2024 · 1 comment

Comments

@SethTisue
Copy link
Member

SethTisue commented Feb 16, 2024

in the chat rooms we've seen people bitten by this over and over and over again

I've lost track of how many dozen confused/disappointed people we've had to inform that -Yexplicit-nulls is half-baked and it shouldn't be surprising when stuff doesn't work all over the place

it's very easy to land on one of the experimental features via Google or some other way and then fail to notice in the outline in the left that you're in the "experimental" section

some of the pages on individual experimental features do a good job of warning you, others less so

the page on -Yexplicit-nulls especially doesn't do a very good job; it describes the feature as "opt-in", but it doesn't require a language.experimental import and we cannot expect most Scala programmers to be aware that -Y is supposed to be a signal that something is experimental and/or internal. Scala veterans know this; many others do not.

@odersky
Copy link
Contributor

odersky commented Feb 16, 2024

I think there should be issues filed or PRs against the explicit-nulls doc page to make clear that the experimental nature should be more emphasized. Same for other doc pages that are not clear enough on this.

Also alert reviewers to have an eye on this.

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

No branches or pull requests

2 participants