I'm going away for a week, and left my laptop behind. Feeling vulnerable.
Contextual jumps through some roundabout hoops to invoke the macro without users needing to specify a `def prefix = macro Contextual.whatever` call, with a lot of complex types. This used to work well, but I think it's obscure enough that 2.13 doesn't know it needs to expand it.
-
-
The solution, I fear, is to replace all of this machinery which no longer works, and resort to the direct `macro Contextual...` invocation. Unfortunately, I think it's at least a full day's work, which I won't have before Christmas...
-
At best, I might be able to create a minimized failure (working in 2.12, failing in 2.13) and submit it as a Scala bug, but as it's related to macros, I don't know how likely it is to be fixed.
- Show replies
New conversation -
-
-
Sounds like something that should've definitely kept working! You can file a big with steps to reproduce `git clone contextual branch/2.13; sbt compile` and let scalac folks figure it out. Worked for me :^)
-
I just checked `contextual` with 2.13.1, actually the macro itself expands just fine, only c.prefix.tree is different now: [error] binary.scala:21:10: Ident(TermName("stabilizer$1")) [error] assert(bin"0101010100001111".toList == List(85.toByte, 15.toByte)) [error] ^
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.