Bugzilla – Full Text Bug Listing
| Summary: | [xtend] Make extension name optional | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Karsten Thoms <karsten.thoms> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | jan, sebastian.zarnekow, sven.efftinge |
| Version: | 2.0.0 | Flags: | sebastian.zarnekow:
indigo+
|
| Target Milestone: | SR2 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
We've had this initially, but it introduces an ambiguity in the grammar, because the parser cannot decide whether it is an optional extension name or an optional return type of a following function. Oops, forget that last comment, we now have a def keyword. It would be ambiguous whether the following is two or one field: ''' Foo Bar ''' If we make it dependent on the existence of the 'extension' keyword it might work. We'll have to check what kind of effects this has on content assist and error recovery. 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 name of included extensions in Xtend classes is mandatory, but normally there is no reason to use the extension instance directly in the Xtend code. It would be better if the variable name is optional and inferred internally. class MyXtendClass { @Inject MyExtension // omit myExtensionName }