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 -Xsource flag (front-end behaves like specified version where possible) #8126

Closed
scabug opened this Issue Jan 8, 2014 · 3 comments

Comments

Projects
None yet
2 participants
@scabug
Copy link

scabug commented Jan 8, 2014

As described in an email by Jason:

I've been plugging a few soundness holes recently, and thought it might be good to make some of the fixes opt-out with a compiler flag.

For example: https://github.com/scala/scala/pull/3178#issuecomment-29444519

We've discussed having a \-source: option in the context of using the 2.11 presentation for 2.10 projects. I could put these sort of things behind that flag rather than inventing a plethora of new \-Ybug\-compat\-SI\-1234 flags.

The current (among others, IDE team) goal is to not only implement that flag but use it to constrain all 2.11 fixes that prevent the type checker from running on a 2.10 code base.

@scabug

This comment has been minimized.

Copy link

scabug commented Jan 8, 2014

Imported From: https://issues.scala-lang.org/browse/SI-8126?orig=1
Reporter: @huitseeker
Affected Versions: 2.11.0-M7
Blocks #8402

@scabug

This comment has been minimized.

Copy link

scabug commented Jan 17, 2014

@huitseeker said (edited on Jan 17, 2014 10:04:00 AM UTC):
PR 3340 Merge commit b296396

@scabug scabug closed this Jan 17, 2014

@scabug

This comment has been minimized.

Copy link

scabug commented Mar 5, 2014

@adriaanm said (edited on Mar 5, 2014 7:18:14 PM UTC):
I'd like to consolidate this with -Xfuture, which corresponds to running 2.11 under -Xsource:2.12.

See #8361.

@scabug scabug added the enhancement label Apr 7, 2017

@scabug scabug added this to the 2.11.0-M8 milestone Apr 7, 2017

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