-
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
Introduce series concept in SourceVersions, add 3.2 to -source (same as 3.0, 3.1) #14629
Conversation
Ideally |
Let's hold off on this until today's meeting to decide whether we're actually releasing 3.2.0-RC1 or 3.1.3-RC1 this week. |
@smarter +1 for 3.1.3-RC1. |
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.
I am not sure about the series
concept. That adds another complication to it which is invisible from the version numbers.
I'd recommend to just add the new version number for now, without changing the infrastructure. Make a separate PR if we still think there should be a series concept after discussing it.
I added series due to how I'll implement the simplification for now |
a0fc86b
to
d7f5ee5
Compare
rebased after #14690 was merged |
803bf26
to
43bc2ba
Compare
revert this commit if we actually need a 3.2 migration, i.e. because we enable strict pattern matching
@odersky this PR now introduces the series concept without modifying the library,
|
we should instead deprecate the |
make it more simple to introduce new language versions that enable no extra features (such as
3.1
).Sets default language mode to
3.2
(currently it is semantically identical to3.0
,3.1
).makes
-source
compiler flag consistent withscala.language
importsIf we enable some features from
future
by default, such as #14294, then we should revert 83bfea9