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
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, . 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
Mozilla isn’t exactly perfect either
Why stop there? How about a lil’ white hat hacking with SQL injection :)
you missed a ‘no’ :)
I’m only terrified
True + true = 2
. I’ve heard memes about Javascript, but jeez. It’s really that bad?
I mean… ‘I would like green apples please’ is a perfectly sensible sentence
you have to pay to have your stuff put on the app store??
uh I think you mean microseconds lol
A nanosecond is just a few clock cycles
doubles can hold numbers way larger than even 64-bit ints
wouldn’t doing significantly more work than necessary be the opposite of laziness?
‘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
did you mean to comment this here?