-
Notifications
You must be signed in to change notification settings - Fork 379
Scala 2.12 support #233
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
Here is the initial list of things that need to be done here:
|
Any update on this? |
@zizhengtai We're currently focusing on improving javalib at the moment, 2.12 support is next on the list once we are reasonably happy with state of things on 2.11. |
We have to make sure we take this in mind: scala/scala#5944 |
Hello from 2018! Do you have some news, do you need any assistance, just in case? |
@fancywriter This issue is the blocker for the next release (0.4.0). Given that there are a number of major changes planned (new optimizer, updated interop, 2.12+ support etc), this release is likely to take longer than usual. Please follow the corresponding github milestone to track our progress towards it. |
@densh I was looking at this scala/scala-collection-compat#45 and thinking that this could become more important when 2.12 support lands in Scala Native because then it seems that we could support 2.13 as well. It seems we have stubs for the methods that didn't link but when I inspect the class listed as suspect, I don't see any of the methods anyway now. Do you think someone could resurrect this PR if you think this makes sense? Will 2.11 still be supported as well? |
2.12 is near the end of the development cycle. We need to extend our nscplugin to support it.
The text was updated successfully, but these errors were encountered: