CyclopsMC / CyclopsCore / 34051129941

31%

master-1.21: 31%

Pull #239

github

Hash an ingredient key once per index update

An ingredient map hashes its key on every operation, and for ItemStack that
hash walks a data component map. The update paths all read then write, and each
call builds its own wrapper, so the same key was hashed twice for one logical
update. Storage networks then run each change twice over, once for its own
channel and once for the wildcard channel, so this multiplies.

IIngredientMapMutable gains a compute method with Map.compute semantics. The
default is the old read-then-write, so nothing has to change to stay correct.
The wrapped adapter builds one wrapper and hands it to the backing map's own
compute, and the classified map delegates to the classifier's sub-map while
keeping its size and its empty-classifier cleanup.

IngredientCollectionPrototypeMap add and remove use it. Callers that hold a
cheap-to-hash component type see no difference.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mxjin31W1Lmq5XK1CCe84v

1307 of 4615 branches covered (28.32%)

Branch coverage included in aggregate %.

3894 of 12108 relevant lines covered (32.16%)

1.56 hits per line