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 ?
-
When do we need to build a Coder at runtime?
The current situation is that Magnolia causes lifted representations of case classes to be instantiated at runtime, and they're represented by classes in the Magnolia library, so it's a runtime dependency, even though the macro isn't.
