Benoit Chatain Lacelle

I agree with @richardstartin . Though, I may not be able to address the issue right now.

@buska88 Supposing this would be fixed soon, is it OK for you to upgrade to latest RoaringBitmap (i.e. 0.9 -> something around 1.4.1 or 1.5)?

OK. I believe `Roaring64Bitmap ` has no such concurrency issue on readonly scenario.

#777 should indeed resolve this, but the root issue may still happen (e.g. for users calling `.getLongCardinality` in concurrency reads). One workaround is to remove the cache (which is populated...

> I am not sure I understand intended use case here. The actual fonctional case is the following: 1. I got a deep tree of nested objects 2. I want...

@cowtowncoder I switched from `@JsonValue` as you suggested in https://github.com/FasterXML/jackson-databind/issues/5030 it would be a good alternative to some relatively simple `StdSerializer`. I'm not very experienced with `@JsonValue` so here some...

> Yes, try reading for more documenations, references such as stack overflows and such 👍🏼 Are you suggesting people should not open bug-report? The behavior looks weird (i.e. unexpected &...

> I thought you considered yourself not very experienced was asking for feedback? I meant, not being experienced with `@JsonValue`, I can not really say if my use-case is exotic...

Note for myself (@cowtowncoder Got a syntetical question for you at the bottom): In the faulty case, `com.fasterxml.jackson.core.JsonGenerator.writeTypeSuffix(WritableTypeId)` gets `typeIdDef.include == WRAPPER_ARRAY`, which kind of explains the array output `["typeInfo",...

@cowtowncoder I'm having a new look into this. Here is a brief overview of my goal, the observation, and a synthetic analysis of a very similar case (Enum/EnumSerializer, while previous...