Navigation Menu

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

Flag -language doesn't list options, nor validate them #5905

Closed
scabug opened this issue Jun 13, 2012 · 5 comments
Closed

Flag -language doesn't list options, nor validate them #5905

scabug opened this issue Jun 13, 2012 · 5 comments

Comments

@scabug
Copy link

scabug commented Jun 13, 2012

The compiler offers to way to discover what are the valid options for the -language parameter, nor does any kind of validation on what is passed to it. That makes it very difficult to check for things like -language:experimental.macros vs -language:experimental.macro.

@scabug
Copy link
Author

scabug commented Jun 13, 2012

Imported From: https://issues.scala-lang.org/browse/SI-5905?orig=1
Reporter: @dcsobral
Affected Versions: 2.10.0
See #5764

@scabug
Copy link
Author

scabug commented Jul 3, 2012

@adriaanm said:
the help message should be generated by looking at the language object's members
most of the code needed for this is there, so this would make for a great community contribution!

@scabug
Copy link
Author

scabug commented Feb 28, 2014

@som-snytt said:
Also learned you can say scalac -language postfixOps -- file.scala, which is why scalac -language file.scala doesn't yield a meaningful message.

scala/scala#3597

@scabug
Copy link
Author

scabug commented Mar 1, 2014

@clhodapp said:
Some might disagree, but it would be a shame to me to lose -language:_

@scabug
Copy link
Author

scabug commented Mar 1, 2014

@som-snytt said:
I thought that was covered under -Xscalista.

No one will disagree, I just forgot the use case when struggling against the fluency of the options API. Thanks!

I wonder if it's worth retrofitting e.g. -Xprint:_. Just a thought.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants