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.
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
Make
-release
more useful, deprecate-target
, align with Scala 3 #9982Make
-release
more useful, deprecate-target
, align with Scala 3 #9982Changes from all commits
3e6dbae
db388d4
cc60058
4b3b050
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
In Scala 3,
-java-output-version
is the preferred flag name (with the alias of-release
still permitted) - would it be reasonable to uncomment this line, and allow Scala 2.13 to use-java-output-version
as well?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 believe we'd accept a PR that did that — at least I can't think why not
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.
Because the dotty project is really bad at choosing option names.
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.
(to be clear: not suggesting we make it canonical in Scala 2, just an accepted alternative)
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.
see also
-Xunchecked-java-output-version
. I didn't want to encourage them (the folks inventing these names). I came close to enabling them (the alt names) on this PR.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.
Thanks! Opened with #10654.
This comment reminded me of my favourite video on software development, the 2012 talk by Andrew Dupont How to Argue About Code (sadly, as it's 'Not Yet Rated' on Vimeo, you have to login to view it in UK & EU, but at least after that there's no ads).
Regarding the option name, for myself, when I'm trying to help junior devs understand that if they want to run their code on Java 11, they need to specify
-java-output-version 11
, the conversation is a little easier than it is if I say-release 11
. The first name, because it includes 'java', is more self-explanatory. The junior dev is aware of Scala and Java, but doesn't automatically realise that when Scala says-release
, it's referring to a Java-related concern.