C++ workflow proposal aims to catch silent noexcept contract breaks
A proposed development workflow addresses a subtle issue where C++ code patches can pass standard tests while silently breaking noexcept guarantees. The system uses a ledger to track each testing attempt, grading both functional output and exception-specification compliance separately. It isolates each test attempt in fresh directories to prevent cross-contamination of object files. The process compiles test programs against both the new code and a known-good header to verify the non-throwing contract. A patch is only promoted if it passes all required checks in a single attempt, preventing the illusion of progress from stitching together results from multiple failed attempts.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in