Message12554

I thought about a solution. We could make field transient and store its class (via getDeclaringClass) and its name (via getName) along with the field. Then initialize the transient field "field" lazily. Class and String are serializable, so this should be fine. If serialization of classes is too complex we could alternatively store the fully qualified name of the class and then lazily init the class via Class.forName.

Do you think that would solve it?

However, I noticed something worse:
In PyReflectedFunction an array of ReflectedArgs is stored. ReflectedArgs contains a plain Object "data". This violates the promize of serializability in PyReflectedFunction. I don't see how to resolve that properly. Only idea I have is to require ReflectedArgs.data to be serializable. Can we change it to "Serializable data"? Thoughts?