AFAIK they’re not seriously considering it as a keyword, but they agreed that in all discussion about the semantics of exceptions they will use “yeet” as a placeholder for the keyword, so people will actually discuss the semantics and not whether the keyword is gonna be “raise”, “throw”, “except” or whatever (so-called Bikeshed Effect)

Using the C++ standard library beyond the C backwards compatible parts? What devilry is this‽

One, two, three, they gonna run back to me

Climbing over mountains and a-sailing over seas

One, two, three, they gonna run back to me

They always wanna come, but they never wanna leave

• Elle King - Ex’s and Oh’s

…I suppose that’s what Elon hopes will happen with his Ex- erm I mean X-users.

Old but gold.

IT support, on the other hand, is more akin to exorcism. In a shaking voice the terrified user describes all the classic signs of a possessed computer, yet when you enter their cubicle and ask them to show you the polterbug, it has already fled in terror and the computer is working flawlessly again. You perform the ritual of reboot anyway, just to be sure.

If the Headquaters are situated in the ocean, they are Headqwaters.

Don’t call it “accidental database deletion”. Call it “unannounced live exercise of backup procedure”.

I’m tempted to put on some thigh highs

Then you don’t even have to seduce the developer anymore, as the programming socks will grant you the power to fix the bug yourself.

That’s intentional. So if one part of the code suffers a random mutation and spontaneously develops a bug, the redundant code can still ensure the proper functioning of the program while the bug gets fixed.

Just take care if you merge two branches that contain the same bug; you might end up with a program without functional redundant code. That’s why you should never merge closely related branches.

Relevant XKCD