I'm going away for a week, and left my laptop behind. Feeling vulnerable.
-
-
Replying to @propensive
That doesn’t bode well for contextual 2.13 being released soon
1 reply 0 retweets 1 like -
Replying to @NicolasRinaudo
This is the tweet I was looking for when I found your earlier one... I spent a few hours trying to work out why it's not working, and it looks like a bug in Scala 2.13. As it says, the macro doesn't get expanded...
2 replies 0 retweets 0 likes -
Replying to @propensive @NicolasRinaudo
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.
2 replies 0 retweets 0 likes -
Replying to @propensive @NicolasRinaudo
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 :^)
1 reply 0 retweets 1 like -
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] ^
1 reply 0 retweets 0 likes -
Replying to @kai_nyasha @NicolasRinaudo
That sounds like it should be easy enough to fix... But how did you see that the macro was expanding? I put some printlns into it, and saw no output, and changed the macro to do nothing (and generate q"null") and was still getting the macro expansion error...
1 reply 0 retweets 0 likes -
Replying to @propensive @NicolasRinaudo
I got a MatchError here https://github.com/propensive/contextual/blob/master/core/shared/src/main/scala/contextual/macros.scala#L30 … Then added a new case with c.abort(showRaw(c.prefix.tree)) and it prints `Ident` above. So, clearly the code executes, at least for `bin`. Could be that it got fixed in 2.13.1?
1 reply 0 retweets 0 likes
No, I was testing with 2.13.1... but I'm interested to look a bit deeper now... Thanks for investigating!
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.