Repository navigation
1.3.1 (2026-11-05)
This release makes the compiler check that the library never drops the result of one of its own internal bool functions by mistake. Nothing a program sees changes: no golden line moves, and the snapshot and journal formats keep their versions.
Fixed
-
Every internal function that returns
boolcarriesM2_NODISCARD(#342). 231 of them lacked it, so a call that dropped such a result could go on past a refusal, or with an out value left unset, and no compiler warned. With the mark, GCC 14 found 25 calls that drop a result. Each one is meant to, so each now says so with(void):- 19 setters, whose parameter channel has already counted the misuse;
- 5 second writes of a pair, which cannot fail once the first has passed;
- 1 corner contact step in the polygon manifold, whose result nothing reads.
tools/check_nodiscard.pykeeps every new internalboolfunction marked.