News for hackers. Stuff that matters.

A comment on The Compiler Is Your Best Friend, Stop Lying to It. Parent comment

Re:The Compiler Is Your Best Friend, Stop Lying to It by AnimalMuppet on Wednesday December 31, 2025 @01:04PM (#46446606)
Worse: You may created the proof. You may have linked to the proof. But if anyone has touched any of the code involved since then, it still has no value unless someone has re-done the proof and linked that. (Worse, it has negative value, because it can mislead.)
[ Parent | on HN ]
Re:The Compiler Is Your Best Friend, Stop Lying to It by skydhash on Wednesday December 31, 2025 @01:15PM (#46446706)
Not really. A quick git blame (or alternative) will give you the required information about the validity of such proof.
[ Parent | on HN ]
Re:The Compiler Is Your Best Friend, Stop Lying to It by dullcrisp on Wednesday December 31, 2025 @01:51PM (#46447041)
You must have some git plugin I haven’t heard about.
[ Parent | on HN ]
Re:The Compiler Is Your Best Friend, Stop Lying to It by skydhash on Wednesday December 31, 2025 @03:24PM (#46447921)
Git blame will show the commit and the date for each line. It’s easy to verify if the snippet has changed since the comment. i use Emacs and it’s builtin vc package that color code each block.
[ Parent | on HN ]
Re:The Compiler Is Your Best Friend, Stop Lying to It by AnimalMuppet on Wednesday December 31, 2025 @04:05PM (#46448341)
But you need the snippet and, potentially, the entire call tree (both up and down).
[ Parent | on HN ]
Re:The Compiler Is Your Best Friend, Stop Lying to It by dullcrisp on Wednesday December 31, 2025 @04:27PM (#46448526)
And anything that can affect relevant state, any dependencies that may have changed, validations to input that may have been modified; it’s hard to know without knowing what assumptions the assertion is based on.
[ Parent | on HN ]