Josh Suereth

@phaller Should we retitle this? Is it a bug/enhancement? @helena Is your issue resolved?

Note: This is related to a series of java pickling issues. Essentially, most of the field information for java types is erased at compile time by the scala compiler (as...

So, I have a few thoughts here: 1. `staticOnly` is meant to be about the generated picklers themesleves. i.e. DO NOT use any reflection in the code generated for the...

@phaller Hey, we may be stepping on each other here. I actually have a branch I'd like you to look at where I completely redo the backend of pickling, and...

@phaller The new FastTypeTag sounds GREAT. I'd love to see those changes. My changes also require a 0.11.x because of breaking some semantics with past macro generated pickler/unpicklers. In any...

+1. I think pickling (serialization) shoudl enable schema and schema evolution. NOT be the schema/schema evolution.

This is a general issue with all serialization frameworks that use any form of runtime reflection in the presence of classloaders (e.g. ObjectInputStream). What you have to do is set...

Also, the 0.11.x branch should be removing the need for reflection on pickling tags, whcih MAY help solve your issue if you can compile with `staticOnly` imported.

Yeah, this is a bug, we do wish to support value classes. I think one of the issues here is around 'runtime' serialization and supporting a `serialize[A] / deserialize[B]` mecahnism...

@rrwright I can help you get your code submitted into the project, but I just don't have time to do the 2.11->2.12 transition. My fear is that the loss of...