Max

> Yes, but that isn't relevant. At issue is the production of invalid UTF-16 strings. Invalid UTF-16 strings are only produced from already invalid UTF-16 strings. This can also be...

> The paragraph specifically says you're allowed to concatenate things that aren't UTF-\* to produce something that's valid UTF-\*. The point of the paragraph is to say that it's ok...

> The buffer in question doesn't contain Unicode. It contains bytes received. That's the whole point. > > And here's how it can happen: > > ```c > read(fd, buf,...

> my idea for binary support was something like this: My feeling is that most of the functionality you're suggesting (particularly, `frombinary`, `tobinary`) would still be useful on top of...

@nicowilliams Thanks for looking, better late than never! > * jq should not be the first thing sporting "WTF-8b" support -- is it your invention? are there other uses of...

I've rebased this PR onto the current master without making any significant changes (only resolving a merge conflict with #2633). I intend to push some code improvements later.

> Yes, you'd have to know to decode from UTF-8 using those to binary, but their presence would be sufficient to indicate that a string is in fact a binary...

I'm not sure what the significant difference is between adding new properties and modifying existing ones. Both are problematic for values that are compared by their content, since the equality...

> In every way these classes are like other classes except for the immutable record-like objects they spawn. To elaborate on this, these are ultimately just record values with a...

> add binary literal forms (b"", b64"")? (not strictly needed, since one could use ""|frombase64 or some such, and we could even make the compiler constant-fold that) As a possible...