Axel Wagner

@creativecreature To be clear, this issue has, AIUI, zero impact on what kind of Go code you can write or how you would write it. AIUI this is simply about...

TBQH I don't believe there really is significant difficulty about deciding what to do - if anything, there is difficulty in how to spec it and *maybe* (though I don't...

I'll note that a trivial order-preserving way to encode an arbitrary uint64 into a valid UTF-8 string is [to use big endian base 128](https://go.dev/play/p/6HEMB7azwqn). Makes the string two bytes longer,...

@timbray To be clear, when i say "two bytes longer", I mean "than what @arnehormann is doing". The suggestion was to do the same thing, but instead of just interpreting...

Thought about it on my run just now. I don't think you can do better than 10 bytes, with a fixed-length encoding, if the result is supposed to be UTF-8....

Okay, I think I have to throw in the towel, this is taking too much time :) Here's the idea, in case it helps dislodge something: First, let's handle positive...

ISTM the only reason to use Go 1.20 here is that you use `cmp.Compare` - and only in a test, at that? I'll note that you could also copy [the...

> With regard to the last point, I don't see a huge difference between: […] and […] I agree, but it should be noted that this is not the only...

@ianlancetaylor highlighting you to be sure - see my last comment, I think this requires some refinement of the generics proposal as a whole, in terms of what it means...

> I'm not sure I understand how instantiation of generic types relates to initialization order. Maybe nothing. I was thinking about [stuff like this](https://play.golang.org/p/28QWGK6qqJ-) and other recursive type definitions. I'm...