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
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...
1 reply 0 retweets 0 likes -
Replying to @propensive @NicolasRinaudo
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.
1 reply 0 retweets 0 likes
Alternatively, if anyone has a convenient working "git bisect" setup on `scalac` nightlies, that might be a good way to find the commit where it stops working, and could hint at a fix. But I just don't have time to set that up now. :(
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.