Benoit Chatain Lacelle
Benoit Chatain Lacelle
@Maithem Would you mind also purging 64bits implementations? Thanks
> why we choose to use TreeMap to store the key value map I did not know an easy way to keep the long[] ordered while inserting a new container...
@lemire do you mean the release process is still not smooth ?
I guess @lemire does not need coffee just to wait commands executing by themselves. I wonder if the release process is still encountering issues requiring attention.
This change was done on purpose regarding performance. In `org.roaringbitmap.realdata.wrapper.BitmapFactory.toByteBuffer(Bitmap)`, we could rely in `java.nio.ByteBuffer.allocateDirect(int)` to easily rely on a direct ByteBuffer still keeping good performance as we would not...
In https://github.com/RoaringBitmap/RoaringBitmap/pull/192, I suggested introducing/modifying multiple interfaces to facilitate decorator implementation working over `RoaringBitmap `and `ImmutableRoaringBitmap `without requiring duplication. It led to propose the introduction of interfaces over `[Immutable]RoaringBitmap` `RoaringArray`...
Would you be interested in a test tracking the quantity of heap allocated ? It would not check actual GC pressure (as for the same quantity of allocations, it would...
I consider current package as some sort of v1. We may argue current package is rathrr some sort of v0, like mvn 0.X Then, moving package to v1, and mvn...
I handled this through: // https://github.com/webauthn4j/webauthn4j/issues/700 @Bean public AttestationOptionsProvider attestationOptionsProvider(ApplicationContext appContext, ObjectPostProcessor objectPostProcessor, AuthenticationManagerBuilder authenticationBuilder) throws Exception { Map
I see it is quite simple to provide various WebAuthn4J beans, and get them used automatically by WebAuthnLoginConfigurer, but it is then unclear what should be removed from `.apply(WebAuthnLoginConfigurer.webAuthnLogin())` custom...