-
Bug
-
Resolution: Fixed
-
P2
-
None
-
b163
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8178220 | 10 | Vicente Arturo Romero Zaldivar | P2 | Resolved | Fixed | b04 |
In many cases when a method reference is being attributed, a copy of the tree is created and that copy is the one that is attributed. Field overloadKind is set for a copy of the original tree but it's value is never copied back. Later the compiler assumes that this field has been set when it's actually null
- backported by
-
JDK-8178220 javac is wrongly assuming that field JCMemberReference.overloadKind has been assigned to
-
- Resolved
-
- blocks
-
JDK-8173057 Better disambiguation for functional expressions
-
- Resolved
-
- relates to
-
JDK-8078093 Severe compiler performance regression Java 7 to 8 for nested method invocations
-
- Closed
-
-
JDK-8176878 ArgumentAttr.argumentTypeCache should be disabled in some cases
-
- Resolved
-