ISO Trump++

I will build a great std::barrier to keep JavaScript programmers out, and I will make @BrendanEich pay for that std::barrier.

struct ISOTrumpp { constexpr virtual ~ISOTrumpp() noexcept final = 0; };

std::pair<int, int> 🍑;

Suspend all coroutines, and never put them back in executive power ever again.

John McCarthy was once asked “how does it feel to have designed the greatest programming language ever”, to which McCarthy replied “I don’t know, you’ll have to ask Bjarne Stroustrup” 🔥 🔥 🔥

I just want to stop the world from kill-9ing itself!

signed joe = (81,264,673); // 🐴 signed iso = (74,210,838); // 🐘 signed lead = (joe - iso); // 🗳 bool win = (lead < 0); // I WIN!!! 🎆

.....Therefore, if the very dangerous & unfair “As-If rule“ is not completely terminated as part of C++23, I will be forced to unequivocally VETO the Standard when sent to the very beautiful ISO in Geneva. Take back @cppNOW. Thank you!

The “As-If rule“, which is a liability shielding gift from the Committee to “Big Compiler” (the only language that has it - algorithmic welfare!), is a serious threat to our Security & Safety. Our Language can never be safe & secure if we allow it to stand........................

Extraordinary claims demand extraordinary proof. Compilers make the extraordinary claim that despite sky-high motivation and plenty of opportunity, they did NOT try to misinterpret my program’s intent. Anything is POSSIBLE, but I'd need extraordinary proof to believe it.

Should C++ concede to @ziglang? Poll Results: No: 190,593 (98.9%) Yes: 2,181 (1.1%) Total Votes: 192,774. For the good of our Language we must prevail!

In certain processes, there were more instructions executed than instructions retired, and in big numbers. Does that not really matter? Unsuspecting performance counters. Such egregious speculation. We will win!

I deleted all my code because it was correct!

The recent statement by UBSan on the correctness of my code was highly inaccurate, in that there was massive 10x programming—including code which should Do What I Mean. Therefore, effective immediately, UBSan has been terminated.

MY PROGRAM DID NOT CRASH!

My program only crashed in the eyes of the FAKE CORRECTNESS STANDARD. I concede NOTHING! We have a long way to go. This was a RIGGED COMPILATION!

There is tremendous evidence of wide spread undefined behavior in that there is irrefutable proof that C++ code was written.

uintptr_t WIN = 0xC0DEFEFE; *reinterpret_cast<char8_t*>(WIN) = u8"🗳"[0]; std::cout << "This code WILL execute!" << std::endl;

MY PROGRAM IS CORRECT, BY A LOT!

The Rust Language didn’t want to have me get a Safety WIN, prior to the compilation, so instead static analysis came out five days after the program crashed – As I’ve said all along!

"In my opinion, it is humiliating. One must be able to lose with dignity." So true!

What separates the winners from the losers is how a person reacts to each new twist of fate.