Good catch! I didn't change the implementation here, as I was just adding a note. However, I've now updated the implementation to fix this and added a test (which I checked against the old implementation). (There's more we could do to optimize the readString/writeString methods, but I haven't tackled that in this commit.)