Skip to content

Resolve SeqType based on a compiler flag #5637

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

Merged
merged 2 commits into from
Jan 4, 2019

Conversation

allanrenucci
Copy link
Contributor

Relying on the classpath didn't work as it was sometime preferred over
the source path. We need to knows which standard library we are
compiling against even before symbols are entered (e.g. during
desugaring).

This flag will go away once we drop support for the 2.12 standard
library. But for now, we need it to compile the 2.13 standard library.

Relying on the classpath didn't work as it was sometime preferred over
the source path. We need to knows which standard library we are
compiling against even before symbols are entered (e.g. during
desugaring).

This flag will go away once we drop support for the 2.12 standard
library. But for now, we need it to compile the 2.13 standard library.
@allanrenucci
Copy link
Contributor Author

TODO: once merged, update the build of our 2.13 standard library fork to use the newly introduced flag

@smarter smarter merged commit 44600e8 into scala:master Jan 4, 2019
@allanrenucci allanrenucci deleted the resolve-seq branch January 4, 2019 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants