Post #2699364
2025-09-24 09:02 UTC
@llogiq@hachyderm.io @Mara@hachyderm.io Could be.
The hard bit is that you can't definitively prove there aren't any. And the tools to prove anything are hit and miss.
Any time I tried plugging in a static analysis tool into an existing code (both mine and at work), it produced a lot of false positives and nothing useful.
When we tried ASAN at work, it found 9 legit issues, all of them in unit tests, none in actual production code.
Statistically, I worry much more about logical bugs than memory ones. So far, they "cost" me infinitely more than the memory ones.
Replies (1)
-
@llogiq@hachyderm.io 2025-09-24 14:44
@jakub_neruda@techhub.social @Mara@hachyderm.io I agree that logic bugs are a problem even in Rust – although in my experience they are easy to find. i use assertions liberally, so if the data flow fails to fit my mental model, I will get a panic with useful information. Conversely, memory bugs may be masked by the allocator (depending on the system) or only ever become visible in uncommon circumstances. Running ASAN is great practice, but even that will only check all the code paths that have been taken during the test run with the given data. Tools can usually only detect the presence of bugs, not their absence.