ifn't

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.

It exists, kind of. Python has this construct

for item in iterable:
    ...
else:
     ...

which always puzzles me, since it depends on a break statement execution. I always have to look it up when the else block is executed.

You just made me a offer I can't refuse. I go now to sleep with the fishes...

do {
  /* something */
} do hast {
  /* something */
}

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!!!

Kernighan, what was I thinking?

As a Virginian learning coding, this would make my damn day.

Or maybe

taint(condition) {}

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.

Legislation (which feels similar to programming languages sometimes) seems to have some keywords of its own. I remember seeing a lot of Whereas ... and Having regard to ....

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

Runs havoc on parsing, too. It's bad for both humans and robots. I say we ship it.

This feels racist against Appalachia. We naturally speak with contractions and are commonly referred to as "unbalanced".

It has a not keyword it's used for pattern matching.

if (x is not null)

ifnt instead of ifn't

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.

I hate seeing colloquial terms like ‘ain't’ in non-comment (ie. standardized) parts of code

Ding ding ding ding ding ding...

That's Typescript...

Here you dropped this:

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

It's not ifn't

if(condition) {#block never used} else {#actually do a thing}

Vs

ifn't(condition) {#actually do a thing}

Vs

if!(condition) {#actually do a thing}

Cannot start a statement with else. One can with ifn't. There is a new thing where we don't branch (which is a separate discussion).

Or am I missing the joke...

I personally have a gut feeling of rejection for every language having the unless keyword. This is why I hardly know any PERL and Ruby for example.

I have mixed feelings towards Kotlin's takeUnless scope function (I nearly always use takeIf with a negated predicate) because my mind forgets the unless version exists.