unsafecast

Sounds good! I don't use either anymore so I wouldn't know.

What about having it listed with the actual name, but when you're viewing it in the program launcher you have a hint in gray? Something like this:

- Okular Document Viewer

If I have two PDF viewers, should both be called "PDF viewer"? Gnome seems to love hiding the actual names (the gnome document viewer is actually called evince).

Why does it alternate between 2023 and 2013?

I end up using a checkers piece, since pretty much every board I've played on has them.

You say underpromotion, but something people are surprised by is making a second queen ime. People sometimes assume promotion is actually "taking a captured piece back".

Indeed, we're being too kind to you.

Hah, I thought I was the only one who lifts shift too late and gets :Wq.

> Technically, int32_t is bad in that way, but we are not fooled by it.

Meaning? On my system int32_t is directly typedefed to unsigned int, absolutely no hidden pointers or conversions.

What order are the bytes in 0xabcd intended to be used in? I don't see how making it 0x[ab, cd] would be ambiguous, it's the same assumption of reading left to right.

I think the iBooks were made like that.

That applies to GLSL in general. I tried once to emulate that using C unions, but quickly realized that there's no solution for v.xz, v.xw, v.yw, etc.

You can write functions like xyz(v) and that works well enough. Even better if you have ufcs or methods.

That's such a perl/raku thing, and I mean it in the best way possible.

Of course it does - endianness interferes with any sort of numeric literal. Doesn't matter if it's hex, decimal, underscored, whatever.