Thomas Heigl

What do you mean by that? Can you give me an example of what you want Kryo to do?

> can I get the custom annotation on the field in my custom serializer? I hope some properties in these annotations will affect the serialization rules. Unfortunately, this isn't possible...

I added a fall-back for lambda deserialization in [f3cd2df](https://github.com/EsotericSoftware/kryo/pull/886/commits/f3cd2dfd7cbaff81f4c734d42a491f12555c5953).

The only remaining issue is with `AtomicInteger` and we can't fix this without breaking backwards compatibility. We should add serializers for `Atomic*`, `UUID`, `Pattern` etc in Kryo 6.

@pyb1993: I have not forgotten about this PR. I'm currently on vacation and will take a look when I'm back in 2 weeks.

@pyb1993: I just looked into your PR and can reproduce the performance gains. However, I'm not sure about applying your changes, since they only affect a rare corner case. As...

@pyb1993: I'm still +0 on this. It can improve things for edge cases, but I'm not sure the change is worth it. I'll try to get some more feedback on...

We've been hit by this issue with recent FST versions as well. As a consequence, we reverted back to version `2.10`. It has been running in our production environment for...

@perlun: It is old, but there have not been too many changes to the serialization code since then. Just look at the commit diagram or the commit history. I'm usually...

@Mr14huashao: As I said in #759, we need a solution with minimal overhead. Ideally, the duplicate field check would be done only once when the serializer is first initialized. I...