Georgi Krastev
Georgi Krastev
But this is only relevant for syntax now, isn't it?
https://scalacenter.github.io/scala-3-migration-guide/docs/macros/migration-tutorial.html
@smarter the macro annotations are not essential. They just generate an implicit instance in the companion object but the heavy lifting is done by blackbox macros. If we want to...
> Just doing some evaluation for scala 3. We use it in some projects and we would like to know if we could use it when Scala 3 comes out?...
We also need to resolve #192 - our build is really outdated 😕
We are blocked by lampepfl/dotty#11685 - looks like we will have to wait until Scala 3.1 😞 I didn't think such a feature could be missing from the new macros.
@smarter on a high level think `Mirror` for traits. Given `trait UserRepo[F[_]]` we want to have `FunctorK[UserRepo]`. shapeless-3 supports `case class UserRepo[F[_]]` or enum but that is not quite the...
No, what we are talking about here is the equivalence between a trait and the `Mirror.Product` of all it's methods as functions. BTW I'm not sure, does every method type...
> You can mix them yes, but you can't represent method with default parameters or methods with varargs losslessly as functions. That's not a problem. We are just forwarding to...
But then you have edge cases like what about abstract vs concrete methods? You shouldn't really have the `AnyRef` methods in that pile.