Georgi Krastev
Georgi Krastev
Shouldn't it be `lazy val` if your type is recursive?
It's fairly easy to reproduce. Just copy the annotation in a file. Both the runtime retention policy and the outer class being annotated are required. ```java package foo; import java.lang.annotation.Retention;...
This would make sense to revive for Scala 3. But I'm not sure what's the correct signature 🤔
Yes I think we have all the tools necessary, it's just a matter of making the time work on this. The beginning is most difficult because we have to setup...
> Hey folks, I would need it for higher kinded data. Do you know if there are any blockers to implement this in Scala 3? If it's possible and not...
> Why do you think shapeless is necessary here? I thought we could just use macros. It's just much easier and type-safe. I think it's fine to start with case...
There is even an example in the tests: ```scala trait FunctorK[H[_[_]]]: def mapK[A[_], B[_]](af: H[A])(f: A ~> B): H[B] object FunctorK: inline def apply[H[_[_]]](using fh: FunctorK[H]): FunctorK[H] = fh given...
Now that Scala 3 support is shaping up, we can add this with polymorphic functions. But we need to first figure out how to add versions of the existing methods.
What the hell happened? 🤔
Ahh, rebase and push to my fork?