-
Notifications
You must be signed in to change notification settings - Fork 87
Scala 2.11 support? #1
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
Comments
I agree that we should support 2.11. My guess is that it should not be hard because the collections API was quite stable between 2.11 and 2.12, but maybe I miss something? |
We should support 2.10 as well, because several projects still support 2.10… (e.g. scalacheck) |
I think we should not support 2.10. Perhaps I could be convinced otherwise, but I think most libraries have already dropped 2.10 support and the remaining ones that haven't, should. I'm afraid of a garden path here where what we have so far might appear to work in 2.10 relatively easily, but it could get harder later on. personally (not sure how the rest of the Scala team feels about it), I'm actually interested in actively discouraging continued use of 2.10, except in contexts where basically everything is frozen. I mean, if people are using 2.10 and it's working fine for them then great, more power to you, keep on, but I don't think people on 2.10 should expect brand new stuff like scala-collection-compat to work for them, nor do I think they do expect it |
Agreed on not supporting 2.10 |
OK, I won’t insist! ;) |
* Add support for Scala 2.11 Fixes #1
Be more explicit about usage of unsound language features
Use CrossType.Pure
should we support Scala 2.11 here? (would it be hard?)
in the library ecosystem, I think a lot of libraries will be cross-building to 2.11 for a long while yet
The text was updated successfully, but these errors were encountered: