GitHub user yoohaemin added a comment to the discussion: (Java/Scala) How do I specify deserialize behavior on schema change?
Interesting idea, but will this detection add overhead to Java users? Maybe performance wise, it's ok because a field missing won't be too frequent of a case. I also think with the planned unroll annotation (Scala 3), the users of the code will have a workaround. https://docs.scala-lang.org/sips/unroll-default-arguments.html This sip is decided to be implemented. GitHub link: https://github.com/apache/fury/discussions/1848#discussioncomment-10716107 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
