Pedagogically this means that the user will be sidestepping the performance concerns that induced the Std.Iter framework for strings. For example, the following steps are interchangeable in creating the same result:
mapping toUpper over the entire string
splitting on whitespace and taking the first char
but 2 followed by 1 has different performance concerns from 1 followed by 2.
There has been some important changes lately involving String and some of them have no backwards compatibility. For example, the track’s version uses String.ValidPos, which has since been deprecated in favor of String.Pos.
We will eventually update the track’s version, but it’s unlikely that we will be able to always use the latest version because we need to make sure nothing breaks in the process.