As long as you don’t test it you are in a quantum state, the same as for the Schrödinger’s cat. Your code is either buggy or is not.
Hence, bugs are in fact triggered by users.
I tried to solve some of the last Advent of Code enigmas with LispE, and I discovered a plethora of problems, which I didn’t think would erupt after so many years of tests.
This post is an automated archive from a submission made on /r/lisp, powered by Fediverser software running on alien.top. Responses to this submission will not be seen by the original author until they claim ownership of their alien.top account. Please consider reaching out to them let them know about this post and help them migrate to Lemmy.
Lemmy users: you are still very much encouraged to participate in the discussion. There are still many other subscribers on !lisp@communick.news that can benefit from your contribution and join in the conversation.
Reddit users: you can also join the fediverse right away by getting by visiting https://portal.alien.top. If you are looking for a Reddit alternative made for and by an independent community, check out Fediverser.
The way I phrase this is “the only perfect code is code no one is running”
this is why lisp is so good
Uncertainty != quantum.
This just seems like an epistemic issue. The code either is or is not buggy regardless of whether anyone looks at it, that question does have an answer. Whether you do (or can) know whether it is buggy is just a different question.
I either have a big dick, or I do not. As long as you don’t look at my dick, my dick is a quantum object.
I can say this program will never return anything except 4 without running it: (* 2 2)