mirror of
https://github.com/spring-projects/spring-framework.git
synced 2026-10-01 03:39:05 +00:00
computeIfAbsent registered the case-insensitive key before invoking the mapping function. If the function returned null or threw an exception, no mapping was recorded in the target map, but the key registration was left behind. The map then reported containsKey(key) as true while size() was 0, keySet() was empty, and get(key) returned null. A later insertion with a different casing also reused the stale casing of the failed call, since the existing-key branch resolved to the registered key. The case-insensitive key is now only looked up up front. For a new key, it is registered from within the mapping function once a non-null value has been computed, which is still before the entry is inserted. A null result or an exception therefore leaves both maps untouched, while a removeEldestEntry override that evicts the new entry right away still removes the registration, as it does for put. The existing-key path keeps computing under the stored casing. Closes gh-37351 Signed-off-by: junhyeong9812 <pickjog@gmail.com>