Skip to content

chore: release 1.3.1 - #344

Merged
siracozmen01 merged 2 commits into
mainfrom
release-please--branches--main--components--maul2d
Nov 5, 2026
Merged

siracozmen01 merged 2 commits into
mainfrom
release-please--branches--main--components--maul2d

Conversation

@rawframe-release

@rawframe-release rawframe-release Bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

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 bool carries M2_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.py keeps every new internal bool function marked.


This PR was generated with Release Please. See documentation.

@siracozmen01
siracozmen01 marked this pull request as ready for review November 5, 2026 04:17
@siracozmen01
siracozmen01 merged commit cf08f1f into main Nov 5, 2026
31 checks passed
@siracozmen01
siracozmen01 deleted the release-please--branches--main--components--maul2d branch November 5, 2026 04:29
@rawframe-release

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant