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

Add version to -Xmigration #6963

Closed
scabug opened this issue Jan 11, 2013 · 7 comments
Closed

Add version to -Xmigration #6963

scabug opened this issue Jan 11, 2013 · 7 comments
Milestone

Comments

@scabug
Copy link

@scabug scabug commented Jan 11, 2013

$ scala -version
Scala code runner version 2.10.0 -- Copyright 2002-2012, LAMP/EPFL

# yay!!

$ scala -X
...
  -Xmigration                    Warn about constructs whose behavior may have changed between 2.7 and 2.8.

# wat?

Adding a version number argument should clean that up

@scabug
Copy link
Author

@scabug scabug commented Jan 11, 2013

Imported From: https://issues.scala-lang.org/browse/SI-6963?orig=1
Reporter: @JamesIry
Assignee: @JamesIry
Affected Versions: 2.9.3-RC1, 2.10.0

Loading

@scabug
Copy link
Author

@scabug scabug commented Jan 14, 2013

Loading

@scabug
Copy link
Author

@scabug scabug commented Jan 15, 2013

@JamesIry said:
The deprecation is now in 2.10.x. To avoid a merge conflict I'll wait until that's in master and then remove the entire switch.

Loading

@scabug
Copy link
Author

@scabug scabug commented Jan 17, 2013

Loading

@scabug
Copy link
Author

@scabug scabug commented Jan 18, 2013

@JamesIry said:
New plan is to add a version parameter to -Xmigration in 2.11. Then it would only print a warning on things that changed after that version number.

Loading

@scabug
Copy link
Author

@scabug scabug commented Jan 30, 2013

Loading

@scabug scabug closed this Feb 1, 2013
@scabug scabug added this to the 2.10.1 milestone Apr 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant