see https://github.com/eclipse/xtext-umbrella/issues/3
Remove org.eclipse.buildship.core.prefs
Files are generated on Gradle project import or by Oomph setup
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
connection.project.dir changed to composite build location in new
umbrella project
value 'containers' added by Buildship
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
To set a breakpoint that hits when a cross reference can not be resolved
it should not be necessary to use a conditional breakpoint. A regular
breakpoint should be enough.
Signed-off-by: Moritz Eysholdt <moritz.eysholdt@typefox.io>
Don't always run the old ConcreteSyntaxValidator before serialization.
Instead, create diagnostics in the serializer only when serialization
fails.
see https://github.com/eclipse/xtext-core/issues/48
Signed-off-by: Moritz Eysholdt <moritz.eysholdt@typefox.io>
containingAssignment() and containingCrossReference() should return
null as fast as possible when there is no Assignemnt/CrossReference
Signed-off-by: Moritz Eysholdt <moritz.eysholdt@typefox.io>
Because they're neither consumed by the old- nor the new formatter.
And they are not needed to generate text.
Signed-off-by: Moritz Eysholdt <moritz.eysholdt@typefox.io>
Implemented new algorithms for computing upper and lower bounds in GrammarConstraintProvider
Signed-off-by: Miro Spönemann <miro.spoenemann@typefox.io>
This disables a check with a legacy impl.
The check should never be active at runtime.
Unfortunately, the legacy impl has a bug when a node's parent is null.
Signed-off-by: Moritz Eysholdt <moritz.eysholdt@typefox.io>
'parameterValues' was usually emptySet()
so parameterValues.hashCode() returned 0
which caused this hashCode() method to return 0
nothing but collisions when used as key in maps! duh!
Signed-off-by: Moritz Eysholdt <moritz.eysholdt@typefox.io>
this change deprecates EmitterNodeIterator since it relies on
expensive calls to iNode.getOffset().
Furthermore, it simplifies the implementation because
- lazy behavior does not provide advantages here
- 'allowHidden' and 'passAbsorber' were always false.
Signed-off-by: Moritz Eysholdt <moritz.eysholdt@typefox.io>
This change allows to specify on XtextResource what ParserRule the
parser should be using as the entry point.
see https://github.com/eclipse/xtext-core/issues/16
Signed-off-by: Moritz Eysholdt <moritz.eysholdt@typefox.io>
When the partial parser does a full re-parse, it should use the same
entry parser rule that has been used during the last parse.
see https://github.com/eclipse/xtext-core/issues/16
Signed-off-by: Moritz Eysholdt <moritz.eysholdt@typefox.io>
