-
Notifications
You must be signed in to change notification settings - Fork 53
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
scaladoc can fail at specific macro annotations (Regression from scala 2.11.1 to 2.11.2) #53
Comments
Hmm that's not good. Is this a blocker for you? |
It blocks me from upgrading to 2.11.2. |
I'll see what I can do in the coming days. Thank you for reporting! |
This is a bug in quasiquotes: https://issues.scala-lang.org/browse/SI-8771. Please follow the discussion over there - I'll try to figure out what can be done as a workaround. |
Had to work around https://issues.scala-lang.org/browse/SI-8771. Thanks, former myself who's suggested a workaround at scalamacros/paradise#53 and thanks google who indexed the suggestion.
Had to work around https://issues.scala-lang.org/browse/SI-8771. Thanks, former myself who's suggested a workaround at scalamacros/paradise#53 and thanks google who indexed the suggestion.
Hi @FlorianKirmaier! Today I faced a similar bug, but the workaround proposed in SI-8771 wasn't enough. After some thinking, I found a way to attack the issue at its root, and now it shouldn't be a problem anymore, regardless of whether the workaround is used or now. The fix has been published under version 2.0.2-SNAPSHOT, 2.1.0-SNAPSHOT and 2.1.0-M3. |
Great to see progress here! The original code of the sample works now. But unfortunately, I still have a lot of issues with Another error can be reproduced with the identity annotation from http://docs.scala-lang.org/overviews/macros/annotations.html |
fix LogicalTree for implicit params
I can compile the following code with "sbt compile" but "sbt doc" fails.
It works with scala 2.11.1 but fails with scala 2.11.2.
I tested paradise version "2.0.1" and "2.1.0-SNAPSHOT".
The text was updated successfully, but these errors were encountered: