You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed the following problem in rehash implementation, at least in MutableObjQHashSetSO.
void rehash(int newCapacity) {
int mc = modCount();
Object[] keys = set;
initForRehash(newCapacity);
mc++; // modCount is incremented in initForRehash()
Object[] newKeys = set;
int capacity = newKeys.length;
if (noRemoved()) {
...
The method initForRehash calls internalInit that calls initSlotCounts that sets removedSlots to zero. Therefore the test noRemoved() always succeeds even when the hash set contains REMOVED entries. This bug appears in koloboke-impl-jdk8 1.0.0 I downloaded from Maven central.
The text was updated successfully, but these errors were encountered:
I noticed the following problem in rehash implementation, at least in MutableObjQHashSetSO.
The method initForRehash calls internalInit that calls initSlotCounts that sets removedSlots to zero. Therefore the test noRemoved() always succeeds even when the hash set contains REMOVED entries. This bug appears in koloboke-impl-jdk8 1.0.0 I downloaded from Maven central.
The text was updated successfully, but these errors were encountered: