@yogthos

Crane decided to ask his AI agent why it went through with its dastardly database deletion deed. [...] So, the agent ‘knew’ it was in the wrong.

No, you asked the confabulation machine to confabulate a reason/excuse after the fact, and it confabulated something that looks like a reason/excuse. At no point was there knowledge or introspection.

I like the original.

If you had let me write the C++ code, I could have literally destroyed your dataset in a couple of seconds.

C) It's an obvious joke.

Because let x: y is syntactically unambiguous, but you need to know that y names a type in order to correctly parse y x. (Or at least that's the case in C where a(b) may be a variable declaration or a function call depending on what typedefs are in scope.)

POV: You open vim for the first time.

The same is true of std::endl. std::endl is simply defined as << '\n' << std::flush; nothing more, nothing less. In all cases where endl gives you a "properly translated" newline, so does \n.

std::endl provides zero portability benefits. C++ does have a portable newline abstraction, but it is called \n, not endl.

Strictly speaking, it should be

Unsafe block syntax in C++

{  ...}

https://github.com/Jaennaet/pISSStream/blob/main/pISSStream/pISSStreamApp.swift looks like code.

@hstde @Spore Even better, the alphabetical index of function names was generated in English first and then translated, meaning the documentation looks like a scrambled mess in any other language because it is alphabetized according to what the English equivalent would be. #excel