-
Notifications
You must be signed in to change notification settings - Fork 107
develop version based on scala.meta #145
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 just hit a road block with not being able to mock a class with final member. It turns out, support for this was waiting on scala.meta. Any plans for this? |
You can have it already. There are several options. One is to merge the following pull request yourself: Another is to build the following version which already includes the fix: |
Scala.meta does not support Scala 2.10 at the moment. see scalameta/scalameta#295 |
Also Scala.JS missing: scalameta/scalameta#359 |
scalameta/scalameta#761 has been merged now |
Scalajs is supported now. No 2.10 support as of now, but considering to build ScalaMock 4.x without support for 2.10. So removing the blocker on this |
Means we should do #187 |
Exists for 2.11 and 2.12 so we'll need to temporarily drop 2.13 support in the new version |
given that Scala is heading towards release 3.0 and has a different API again, I am not sure if this is worth investing time anymore. there are a number of open bugs that would benefit from a scala.meta implementation, but not sure how well, if at all, this could be reused when https://docs.scala-lang.org/scala3/guides/macros/index.html becomes stable |
closing this as Scala 3 is out now |
It looks like scala.meta 1.0 is out, so the promise on a roadmap page might be out-of-date. Do I understand correctly the project still needs new macros to be released?
The text was updated successfully, but these errors were encountered: