-
Bug
-
Resolution: Fixed
-
P4
-
25, 26
-
b08
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8366719 | 25.0.2 | Victor Rudometov | P4 | Resolved | Fixed | master |
Neither ScopedValue.orElse nor ScopedValue.orElseThrow consult the cache when searching for a binding. Neither do they update the cache when a binding is found.
While this issue does not affect spec compliance, it is surprising to users that x.orElse(other) should be slower than x.isBound ? x.get() : other.
While this issue does not affect spec compliance, it is surprising to users that x.orElse(other) should be slower than x.isBound ? x.get() : other.
- backported by
-
JDK-8366719 Scoped Values: orElse and orElseThrow do not access the cache
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk25u/b32786a4
-
Commit(master)
openjdk/jdk/9dd93c6a
-
Review(jdk25)
openjdk/jdk/26976
-
Review(master)
openjdk/jdk25u/142
-
Review(master)
openjdk/jdk/26164
(1 links to)