note
haukex
<blockquote><i>For example, passing a string consisting of characters <c>80</c> and <c>80</c> with a second argument of 2 will can [sic] result in <c>"\x80"</c> (correct) and <c>"\x80\x80"</c> (incorrect).</i></blockquote>
<p>The way you've worded this makes it sound like the output is not deterministic, which is certainly not the case. Also, <i>"a string consisting of characters <c>80</c> and <c>80</c>"</i> is not specific enough for a test case. But please feel free to provide some actual test code that demonstrates the bug you are trying to explain, or better yet, show how you would've coded it to (at least in your view) "correctly" handle the different strings <c>"\x80\x80"</c> and <c>"\N{U+80}\N{U+80}"</c>.</p>
1230633
1230686