Beanie

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

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.

you have to pay to have your stuff put on the app store??

wow my history is identical :0

what a coincidence

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

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.

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

Strawbery

uh I think you mean microseconds lol

A nanosecond is just a few clock cycles

I mean... 'I would like green apples please' is a perfectly sensible sentence

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

I'm only terrified

Why stop there? How about a lil' white hat hacking with SQL injection :)

Haha I've already watched that video countless times

Edit: dammit, they cut off the last second of the video where there's a segfault :(

I suppose it would be possible if you surreptitiously turned on their webcam and used the output of that in place of where they would want the mirror

return (x >= y); also works

doubles can hold numbers way larger than even 64-bit ints

Oh I get you. No idea tbh.

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

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

And 90% of the time, n is about 3

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.

'it should pretty much never segfault' uh, isn't that the entire point of Rust? Unless you're counting failing a bounds check as a segfault

True + true = 2. I've heard memes about Javascript, but jeez. It's really that bad?

wouldn't doing significantly more work than necessary be the opposite of laziness?

did you mean to comment this here?

even worse, the first if statement randomly has brackets while none of the others do

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.)

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

No results on duckduckgo. It was on google, but it was the 6th result.

what in the fuck.

you missed a 'no' :)

Mozilla isn't exactly perfect either