Thomas Heigl

Please create a PR with an implementation for one of the [default array serializers](https://github.com/EsotericSoftware/kryo/blob/cb255af4f8df4f539778a325b8b4836d41f84de9/src/com/esotericsoftware/kryo/serializers/DefaultArraySerializers.java#L63). I'm still not sure this should be provided by Kryo out of the box, but we...

@rgomezp: I'm very interested in this feature as well. Is there currently any way to achieve this? Or is it somehow possible to completely destroy the OneSignal SDK and re-initialize...

@r0b0ji: Kryo tries to avoid all third party dependencies so kryo-serializers is the right project for this. @magro: Could you take a look at this PR?

@holgerbrandl: Thanks for the report and the reproducer. Any chance you can reproduce this issue in plain Java? This would make it much easier for me to look into this....

> I don't know about the implications of setOptimizedGenerics, so I guess the problem is not fully solved. The only negative implication is that Kryo doesn't try to use generics...

@JanecekPetr: The `RecordSerializer` was a contribution from Oracle. When I accepted it, I didn't really think about aligning it with `FieldSerializer` and its compatible variants, but it definitely makes sense...

@JanecekPetr: Thanks a lot for looking into this! I'll think about these issues and will get back to you asap.

@JanecekPetr: Thanks again for your valuable input! > The eclipse project setup is outdated - JUnit 5 was introduced, but the setup doesn't know about it yet. I'm not yet...

@JanecekPetr: Did you make any progress on this issue? I started preliminary work on refactoring the `FieldSerializer` to support records, but I don't have enough free time to finish this...

@xuedonglxd: This sounds like a very specific use case. You can create a PR, but I cannot promise that I will merge it, if it adds too much complexity. What...