Do not use lambdas in Converters

[radcortez]

No description provided.

[dmlloyd]

Why? Is there some kind of problem case?

[radcortez]

I did notice some extra allocs in the flamegraph.

[dmlloyd]

I would expect a similar number of allocations in either case. The only difference would be the one time initialization of the lambda infrastructure, but that gets paid by someone at some point no matter what so there's no reason to avoid it here IMO.

[franz1981]

It's considered a bit nuts, but you can even decide to have a single Object converter which have a switch based on an enum filed which represent the actual type and perform the right behaviour.
It will allow to have N instances of the same converter class.
Not saying you should do it eh, but if you don't want to trade lambdas dynamic gen vs class loading for N anon types, you can decide to do it.