Fix Scala3 lazy val serialization

[sujeenoh-dev]

Closes #24 issue.

[nvollmar]

lgtm - thanks for bringing up this issue.

A concern is, that Users might not be aware of the initialization being done again after deserialization. This solution is reasonable if we want to support lazy val serialization, but maybe we should add a hint in the README how lazy vals are serialized in Scala 3 and that it might be re-evaluated on the deserialized object.
(Another option would be to not support lazy val serialization on Scala 3)

[ghostdogpr]

Note that the proposed approach here is consistent with how Scala 3 handled it for Java serialization (since there was the same problem): scala/scala3#21243

I think updating the README sounds good 👍

[sujeenoh-dev]

Thank you for the feedback! I'll update the PR and add a note about this behavior to the README.

[nvollmar]

@ghostdogpr Thanks for the reference, handling it the same way as Java serialization indeed makes sense.

[sujeenoh-dev]

If the updated description looks good, Please merge the PR. 🙏

[danischroeter]

nice! thx a lot