> reasoning about program correctness is not possible
Not possible for all problems. We cannot decide correctness (ie adherence to a specification) for all programs, but we can definitely recognize a good chunk of cases (both positive and negative) that are useful.
The Halting Problem itself is recognizable. The surprising result of Turing’s work was that we can’t decide it.
> You didn’t even look at what the tool does, did you?
On the contrary, I did exactly that. It proactively intervenes where mathematical knowledge would be a better remedy overall. It shields programmers from their ignorance.
If floating-point code is correctly written, it can't possibly serve a useful purpose.
> Yeah you are just criticizing this without even looking at it.
Please imagine the luxury of being SO FAR AWAY from all the crap happening on our planet right now, only to be spoiled by some lousy marketing emails from Microslop hawking their latest Copilot incursion.
I use Zotero [1] to manage/read/annotate all my papers and it's got a built-in PDF inverter that works pretty well. I'll take Veil out for a spin some time and see if it works well in places where Zotero's algorithm fails.
Not possible for all problems. We cannot decide correctness (ie adherence to a specification) for all programs, but we can definitely recognize a good chunk of cases (both positive and negative) that are useful.
The Halting Problem itself is recognizable. The surprising result of Turing’s work was that we can’t decide it.
reply