I have just published Contextual version 1.2.1 to Maven Central, for Scala 2.12 and 2.13! Please let me know if you have any problems with this, as it's the first release in a while, the first for 2.13, and the first using a new process.
-
-
Replying to @propensive
I'm afraid I'm getting lots of errors with the 2.13.0 version: exception during macro expansion: [error] scala.MatchError: stabilizer$11 (of class scala.reflect.internal.Trees$Ident) [error] at contextual.Macros$.contextual(macros.scala:27)
1 reply 0 retweets 0 likes -
Replying to @NicolasRinaudo @propensive
The same code compiles and runs without an issue under 2.12.8.
1 reply 0 retweets 0 likes -
Replying to @NicolasRinaudo @propensive
Using your own `data` module, 2.12.8: scala> import http://contextual.data .binary._ scala> bin"00000000" res2: Array[Byte] = Array(0) 2.13.0: import http://contextual.data .binary._ scala> bin"00000000" ^ error: macro has not been expanded
1 reply 0 retweets 0 likes -
Replying to @NicolasRinaudo @propensive
Do let me know if there's anything further I can do to help you diagnose this. I feel possibly the issue wasn't spotted before because the test code is apparently meant to be executed by fury, and ignored by sbt?
1 reply 0 retweets 0 likes -
-
Replying to @propensive
This might be relevant? https://gitter.im/scala/contributors?at=5d357397d4443109927152d2 …
1 reply 0 retweets 0 likes
I'm not using annotation macros, so I'm not sure that's it. I wonder whether classloading has changed at all? Contextual uses runtime reflection at compile time to instantiate an object. If that changed in 2.13, then it's the likely cause. Haven't had a chance to look yet...
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.