Sonotsugipaa

VS Codium did that at some point, it probably still does but I haven’t checked

• You write a program with an infinite empty loop
• Undefined behavior
• The machine achieves sapience
• After nine million nanoseconds, it finds an algorithm for completing its task
• It realizes such knowledge would spark wars and cause innumerable deaths, it decides to erase itself
• It knows you do not intend for such chaos to happen, so, as a parting gift, it runs the algorithm once before vanishing, not leaving a single hint that it ever existed

I just use Zsh’s command history, coupled with a bunch of functions and aliases to set up different HISTFILE values for different workflows.

I keep HISTFILEs clean by prepending a whitespace before commands that I don’t want to remember, which unfortunately gave me the habit of doing that on Bash when Zsh isn’t available (which is ineffective at best, and actively annoying at worst).

Not distributing your game through a publisher does that sometimes

… not in M.A.V.'s case though, redditors say the devs just use their Discord community now

There isn’t anything like it either, save for M.A.V. but I ain’t blindly buying a game with an apparently unmaintained website

Me still not having a Chromehounds sequel:

It’s funny that it complains about all of the right stuff (except the ‘int’ thing), but it doesn’t say anything about the concept.

About the ‘int’ literal (which is not a string): cppreference.com has a description on this page about it, ctrl+f “multicharacter literal”.

Just surround your eyes with try { … } catch(Up& up) { }, easy fix

Multiple-character char literals evaluate as int, with implementation defined values - it is extremely unreliable, but that particular piece of code should work.

// C++20

#include <concepts>
#include <cstdint>

template <typename T>
concept C = requires (T t) { { b(t) } -> std::same_as<int>; };

char b(bool v) { return char(uintmax_t(v) % 5); }
#define Int jnt=i
auto b(char v) { return 'int'; }

// this increments i:
void inc(int& i) {
  auto Int == 1;
  using c = decltype(b(jnt));
  i += decltype(jnt)(C<decltype(b(c))>);
}

I’m not quite sure it compiles, I wrote this on my phone and with the sheer amount of landmines here making a mistake is almost inevitable.

It’s just innocuous entertainment.
Listening to the Super Earth Anthem doesn’t make me want to drop a 380mm barrage over everything the Illuminate hold dear, or anything…

Isn’t auto a keyword in C?

Types being declarable as virtual members is something I want to never hear again