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 ?
-
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...
I have a solution to this which I need a clear day to finish. (It was almost working, but too much changed underneath me...) Does what I described here sound like it would help?https://github.com/propensive/magnolia/issues/46 …
