Skip to content

Error on warnings for strict memory safety - #71

Merged
natecook1000 merged 4 commits into
mainfrom
even-more-strict
Nov 11, 2026
Merged

natecook1000 merged 4 commits into
mainfrom
even-more-strict

Conversation

@natecook1000

Copy link
Copy Markdown
Member

This catches the few call sites that don't already have the unsafe keyword applied.

Checklist

  • I've added at least one test that validates that my change is working, if appropriate
  • I've followed the code style of the rest of the project
  • I've run Scripts/format.sh to correctly format my change
  • I've read the Contribution Guidelines
  • I've updated the documentation if necessary

@natecook1000
natecook1000 requested a review from lorentey October 29, 2026 19:06
@natecook1000
natecook1000 merged commit a227b91 into main Nov 11, 2026
32 checks passed
@natecook1000
natecook1000 deleted the even-more-strict branch November 11, 2026 19:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant