-
Notifications
You must be signed in to change notification settings - Fork 14
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
Any plan to support scala 3? #243
Comments
hi, sorry for the late reply. Unfortunately there isn't a plan for upgrading from scala2 to scala3 yet. I've tried to do it but it seems to require a lot more effort that expected. This is the branch that I'm working on. Please feel free to raise a new PR or contribute to this one if you would like to. Thanks. |
Do you have more detail on the difficulties you've run into upgrading? From a fresh clone, with Scala 3.2.2, if I remove kind-projector and use the |
@mhzajac integration tests are failing for scala 3 and that is the only blocker atm. It looks like this bug but I might be wrong. I haven't managed to figure out why. Any suggestions are welcomed. Thanks. |
Ah, that looks right. I no longer see that error using dotty/main, but it's not officially published yet |
Any news on Scala 3 support @d2a4u ? |
Update: please see #301 (comment) |
We've waited too long for Scala 3 support. Please help! |
hi, sorry for the long delay. I've not been able to spend as much time as I did before on this project. Version 2.0.0 has been released with Scala 3 support. With this release, I've dropped supports for |
Great to see meteor v2 released with Scala 3 support! 🥳 Thanks @d2a4u ! 🙇 |
The project is currently cross published for scala 2.12 and 2.13. Are there any plans to start supporting scala3?
Importing meteor in scala3 projects using
cross(CrossVersion.for3Use2_13)
is not an option, because dependencies have different incompatible artefacts for scala2 and scala3The text was updated successfully, but these errors were encountered: