Should segmentIterator.following(n) match a break position at n? about proposal-intl-segmenter

[gibson042]

I believe this is resolved; the API has a distinct but independently coherent model.

[littledan]

@gibson042 You're arguing, the current interpretation is off by one? PRs welcome to make this proposal more concrete!

[gibson042]

I think so. Modeling this feature after prior art in ECMAScript would probably manifest as something like moveToBreak( [ fromIndex ] ) and moveToLastBreak( [ fromIndex ] ), and almost certainly the state holding location-in-string would be pointing at the next possible index rather than the last matched:

let decomposed = "Ångström".normalize("NFD");
let segmenter = new Intl.Segmenter("sv", {granularity: "grapheme"});
let iterator = segmenter.segment(decomposed);

iterator.index; // → 0

// Read the first segment and observe that index advances.
iterator.next().value; // → { segment: "Å", index: 0, breakType: undefined }
iterator.index; // → 2

// Move to a break on or following an index inside a combining character sequence.
iterator.moveToBreak(1);
iterator.index; // → 2

// Read the segment at that point and observe that index advances.
iterator.next().value; // → { segment: "n", index: 2, breakType: undefined }
iterator.index; // → 3

Should I propose such changes?

[littledan]

Sure, the next step would be to write up a PR and put it on the agenda for our next Intl meeting.