Wow, massive red flag. How quickly did you quit?

Hah, I do not like the greengrocer’s apostrophe. It is just wrong no matter how you look at it. The Oxford comma is a little different - it’s not technically wrong, but it should only be used to avoid confusion.

Oh right - that would be the same category as numbers then. (Looked it up out of curiosity: using apostrophes isn’t incorrect, but it seems to be an older/less formal way of pluralising them.)

Strawbery

That’s half-right. Upper-case letters aren’t pluralised with apostrophes but lower-case letters are. (So the plural of ‘R’ is ‘Rs’ but the plural of ‘r’ is ‘r’s’.) With numbers (written as ‘123’) it’s optional - IIRC, it’s more popular in Britain to pluralise with apostrophes and more popular in America to pluralise without. (And of course numbers written as words are never pluralised with apostrophes.) Acronyms are indeed not pluralised with apostrophes if they’re written in all caps. I’m not sure what you mean by decades.

And 90% of the time, n is about 3

The line causing the memory leaks is actually the lack of a line: free().

did you mean to comment this here?

At a PV node, do not cut off from any TT hit.

The SPRT result of this may be different than before thanks to LMR.

Bench: 5212899

hey, you did ask

If it gets comitted to master, TODO means never do.

'The image cannot be displayed because it contains errors.`

Oh I get you. No idea tbh.

Actually vim has swap files which it saves to when you make any edit, whether you save the change or not, meaning you shouldn’t lose any work even if you kill -9 vim on unsaved work.

Ah yes, #include\n. The magical include that simply copy-pastes the entirety of libc’s headers into your source file.

wow my history is identical :0

what a coincidence

That was my first thought when trying to figure out what it did