Jon Pretty

Hej @propensive . How would you feel about a PR to split up Magnolia's "gen" methods into smaller "public" methods? I'd like to use Magnolia as a toolkit to build my own macros instead of using the derivation directly. Would that make sense ?

Tu deviens suedois... ;) No, I don't fully understand! Can you give me an example of the usage? (Or anything which helps me get it!)

Mais oui! So I'm using Magnolia to derive Beam coders which must be serializable... As a consequence, I'd rather not have Magnolia classes at runtime. I'd also need to be careful not to accidentally capture the outer scope of my TC definition...

So I was thinking that I could use Magnolia in my own macro to get the list of parameters of a given case classe and the typeclass instances of each param. Supporting sealed trait like Magnolia does would also be interesting.

As an outside possibility, you might be able to call the Magnolia implementation method directly from your own macro implementation method. (It's just a method which returns a tree, after all...)

Yeah I thought about it but I don't think it really solve my issue. Issue 46 in the other hand seems to be what I need. Anything I can do to help with this ?