a little gem lurking in the magnolia docs: "however, there is the flexibility to provide additional type parameters or additional implicit parameters to the definition". Adding additional implicits lets you use other typeclasses in the derivation. @propensive
Yes, maybe I should make that clearer! The concept is that the Magnolia macro will just glue together the appropriate method calls, but doesn't require an exact signature (in the OO sense) for each implementation, as long as they have the right "shape" to be called.
-
-
How hard would it be to allow driving tc A for case class where each member has an instance of tc B? I had to fallback to shapeless for this ;(
-
My use case is generating JSON schema for case classes. For default values you end to serialize the default value using with a tc for the parameters. I ref the serializer tc from the schema tc. By adding implicit Param to combine, I captured serializer tc for case classes.
End of conversation
New conversation -
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.