| Summary: | [xtend2] problems with nested types in FOR-loops | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Moritz Eysholdt <moritz.eysholdt> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | sebastian.zarnekow, sven.efftinge |
| Version: | unspecified | Flags: | sebastian.zarnekow:
indigo+
|
| Target Milestone: | M7 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
pushed to master Closing all bugs that were set to RESOLVED before Neon.0 Closing all bugs that were set to RESOLVED before Neon.0 |
the xtend2-code ------ foo(Map<String, String> m) { '''«FOR e:m.entrySet»«ENDFOR»''' } ------ gets compiled to ------ public StringConcatenation foo(final Map<String,String> m) { StringConcatenation builder = new StringConcatenation(); { Set<Entry<String,String>> _entrySet = m.entrySet(); for(java.util.Map$Entry<java.lang.String,java.lang.String> e : _entrySet) { } } return builder; } ------- In there, "java.util.Map$Entry" causes a Java compile error. It needs to be "java.util.Map.Entry"