Skip to content

[Guideline] Add guideline requiring wrapping unsafe code in safe abstractions #176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

AchimKriso
Copy link
Contributor

Like #175, this is a low hanging fruit of a guideline.

While there aren't analogous guidelines for CERT or MISRA (as far as I know) this is mostly due to the fact that C or C++ do not have the same safe-unsafe split.

Still, without this rule the whole concept of safe Rust becomes meaningless.

Copy link

netlify bot commented Aug 18, 2025

Deploy Preview for scrc-coding-guidelines ready!

Name Link
🔨 Latest commit fc7280a
🔍 Latest deploy log https://app.netlify.com/projects/scrc-coding-guidelines/deploys/68a34b2a513afd000814d41c
😎 Deploy Preview https://deploy-preview-176--scrc-coding-guidelines.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

:category: required
:status: draft
:release: -
:fls: fls_jep7p27kaqlp
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This simply references the entire Unsafety chapter of the FLS.
I wasn't able to find anything better, since the FLS is mostly about describing the Rust language itself, instead of how to use it correctly.

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