The outline builder ("Tree Model Builder") should omit any entities that are properly marked synthetic by the compiler front-end.
There used to be code to do this for 1.5; perhaps it's just not checking for the "synthetic mark" in the right way for Polyglot 3/X10 2.0.
Need to investigate whether all such entities are being so marked by the 2.0.1 front-end, or whether the X10DT tree model builder is just neglecting to omit them.
Robert M. Fuhrer
added a comment - The outline builder ("Tree Model Builder") should omit any entities that are properly marked synthetic by the compiler front-end.
There used to be code to do this for 1.5; perhaps it's just not checking for the "synthetic mark" in the right way for Polyglot 3/X10 2.0.
Need to investigate whether all such entities are being so marked by the 2.0.1 front-end, or whether the X10DT tree model builder is just neglecting to omit them.
To first order, the outline view shouldn't include any entities that don't actually appear in the source.
I thought Polyglot used to provide a direct way of marking a member/type as "synthetic" (i.e. compiler-generated). If so, this should be used to prune such entities from the outline view. If not, Polyglot also provides the static Position.COMPILER_GENERATED that might be used to identify the synthetic entities.
Robert M. Fuhrer
added a comment - To first order, the outline view shouldn't include any entities that don't actually appear in the source.
I thought Polyglot used to provide a direct way of marking a member/type as "synthetic" (i.e. compiler-generated). If so, this should be used to prune such entities from the outline view. If not, Polyglot also provides the static Position.COMPILER_GENERATED that might be used to identify the synthetic entities.
Need to investigate further.
The compiler doesn't properly mark synthetic constructors with Position.isCompilerGenerated(), so as a work-around, the X10TreeModelBuilder now also asks whether the textual extent is empty.
Robert M. Fuhrer
added a comment - The compiler doesn't properly mark synthetic constructors with Position.isCompilerGenerated(), so as a work-around, the X10TreeModelBuilder now also asks whether the textual extent is empty.
Moving all open items for X10DT 1.7 to X10DT 2.0 since 1.7 has been released.