| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8204390 | 11.0.1 | Maurizio Cimadamore | P4 | Resolved | Fixed | team | 
                    TransTypes report user-facing errors in two conditions:
1) if there's a clash between bridge methods and user defined methods
2) if there's an actual/formal argument arity mismatch due to compiling sig poly methods with -target 6
Now, (1) is no longer an issue since we started carrying out override checks in Attr (seeJDK-7007615); for (2) I believe a better fix for JDK-8013179 would be to eliminate much of the special casing associated to sig poly methods.
            
1) if there's a clash between bridge methods and user defined methods
2) if there's an actual/formal argument arity mismatch due to compiling sig poly methods with -target 6
Now, (1) is no longer an issue since we started carrying out override checks in Attr (see
- backported by
- 
                    JDK-8204390 Remove error generation from TransTypes -           
- Resolved
 
-         
- duplicates
- 
                    JDK-8133247 Use of HYPOTHETICAL flag in bridge generation logic leads to missing bridges in some cases -           
- Closed
 
-         
- relates to
- 
                    JDK-8013179 assertion failure in javac when compiling with -source 1.6 -target 1.6 -           
- Resolved
 
-         
- 
                    JDK-8028739 javac generates incorrect descriptor for MethodHandle::invoke -           
- Closed
 
-         
- 
                    JDK-7007615 java_util/generics/phase2/NameClashTest02 fails since jdk7/pit/b123. -           
- Closed
 
-         
- 
                    JDK-8216196 No visibility bridges are created for generic methods -           
- Closed
 
-         
             (1 relates to)