Bugzilla – Full Text Bug Listing
| Summary: | Missing warning for diamond operator | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Carsten Hammer <carsten.hammer> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jarthana, stephan.herrmann |
| Version: | 4.20 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://github.com/eclipse-jdt/eclipse.jdt.core/pull/1036 | ||
| Whiteboard: | |||
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This is still an issue. I see that we return before invoking redundantSpecificationOfTypeArguments() since AllocationExpression#typeExpected is null. I will investigate. |
In this case eclipse should give a warning (if enabled) to use diamond operator: HashMap<String, Set<String>> hashMap = new HashMap<>(); hashMap.put("abc", new HashSet<String>()); The second line can be written: hashMap.put("abc", new HashSet<>()); However, eclipse ignores this case.