| Summary: | [Xtend] Message of quickfix to create constructors uses "wrong syntax" | ||
|---|---|---|---|
| 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:
juno+
|
| Target Milestone: | M4 | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Moritz Eysholdt
(In reply to comment #0) > Furthermore, "Must define an explicit constructor" is not a proper English > sentence. Since the message is the same for Java constructors, we should stick with it. What do others think about the wording? Implicit super constructor X() is undefined for default constructor. Must define an explicit constructor As we integrate that heavily with Java, we might want to find a wording which abstracts over the two different syntaxes. How about : "No default constructor in super type Foo. Must define an explicit constructor." (In reply to comment #2) > As we integrate that heavily with Java, we might want to find a wording which > abstracts over the two different syntaxes. +1 > How about : > > "No default constructor in super type Foo. Must define an explicit > constructor." We could go one step further: class Zonk extends Foo {} Error message: "No default constructor in super type Foo. Zonk must define an explicit constructor." 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 |