The existing line/column indexes in SourceSpan are useful for some cases, e.g. editors that are line based. But for other cases, it's useful to be able to get the index within the original input string.
An example: If the input string is "foo\n\nbar", the "bar" paragraph has the following SourceSpan:
line 2 (third line), column 0, length 3.
With this change, now it also includes the input index: 5 ("b" is the character at index 5 in the string).
That means it's possible to use e.g. substring instead of having to split the input text into lines first.
The existing line/column indexes in
SourceSpanare useful for some cases, e.g. editors that are line based. But for other cases, it's useful to be able to get the index within the original input string.An example: If the input string is
"foo\n\nbar", the"bar"paragraph has the followingSourceSpan:With this change, now it also includes the input index: 5 ("b" is the character at index 5 in the string). That means it's possible to use e.g.
substringinstead of having to split the input text into lines first.