Point/Position naming

[strumenta]

Point/Position naming

[ftomassetti]

Ok, then I think we converge on renaming Position to Range in Kolasu 1.6.
Regarding renaming Point to Position I agree it could make things confusing.
Would it make sense to keep Point so that we would have a Range being composed by two Points?
This would go in branch 1.6

[alessiostalla]

Monaco/VSCode uses "range" for what we call Position. I wouldn't mind renaming Position to Range (and maybe Point to Position, though that could make migrating a bit confusing)

[ftomassetti]

Another thing to consider, related to this is #27
We should do this refactoring and understand if the name of the source (typically a source file) should go in "Point" -> "Position" or "Position" -> "Range"

[ftomassetti]

@mctaverna @alessiostalla @loradd do you have an opinion on the naming of these elements?

[mctaverna]

@ftomassetti I don't really have an opinion, I remember that in GraalVM they have SourceSection.

[loradd]

Ok, then I think we converge on renaming Position to Range in Kolasu 1.6. Regarding renaming Point to Position I agree it could make things confusing. Would it make sense to keep Point so that we would have a Range being composed by two Points? This would go in branch 1.6

Yes, I think that renaming Position to Range would be enough not to create too much confusion while achieving our goal.

[ftomassetti]

In branch future/16 we completed the renaming