Thank you Reuven for the response!
I'll update the design doc to include adding support for the generic
classes. As for the new reflection API that's what I propose in the doc as
well, it seems like the right choice.
By codegen path you mean using bytebuddy to generate the constructor and
the
Some initial thoughts:
Making schema inference handle generic classes would be a nice improvement
- users occasionally bump into this restriction, and there's no reason not
to improve it.
I would recommend using the new Java reflection APIs (i.e.
getRecordComponents) to directly infer the
