Some C++ style guides suggest the following naming convention for functions that crash on any error

OpenFileOrDie()

this is just a menacing try/catch!

It_would_be_a_shame_if(condition)

The better try-catch. More intuitive if you ask me.

I would have bought it if they said ifnot instead, it's the same number of characters and wouldn't require a major parser overhaul to support keywords with a ' in the name.

nocap(frfr){

}

You could have saved two, all you had to do was use the interrobang. You’re a monster.

All known deposits were depleted

1.21GB!!!

I believe that resolves the same as

ain't!(!untrue)

I think it's just capitalizing on a trend to add n't to otherwise noy contractions, to make them into contractions. Contractionn'ts, if you will

Yes... how is "reducing exclamation marks" a good thing when you do it by adding a ' (not to be confused with , ´,‘or’` ..which are all different characters).

Does this rely on the assumption that everyone uses a US QWERTY keyboard where ! happens to be slightly more inconvenient than typing '?

If someone really wanted to add it, probably the best would be to use unless

Is this a reference to something because I’d love to read it if you have a time to share.

If they'd'nt've done that, it'd've been better. Agreed.

May I introduce you to the joys of #define and creating your own horrible sub language

Please remain calm, we are sending paramedics to your location.

Here you dropped this:

#define ifnt(x) if (!(x))