Skip to content
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

Discuss MISRA draft of guidelines for Rust #52

Open
PLeVasseur opened this issue Oct 31, 2024 · 2 comments
Open

Discuss MISRA draft of guidelines for Rust #52

PLeVasseur opened this issue Oct 31, 2024 · 2 comments
Labels
coding guidelines Related to work in the Coding Guidelines Subcommittee

Comments

@PLeVasseur
Copy link
Collaborator

No description provided.

@PLeVasseur PLeVasseur converted this from a draft issue Oct 31, 2024
@PLeVasseur PLeVasseur added the coding guidelines Related to work in the Coding Guidelines Subcommittee label Oct 31, 2024
@AlexCeleste
Copy link
Contributor

AlexCeleste commented Nov 5, 2024

MISRA will be discussing exactly what we're doing in the space next week, so there's kinda an overlap of schedules here, but I think it could be sensible to discuss this today if there's not too much else taking up the time.

What we want to do isn't quite settled, but I think we're approaching consensus on a two-part strategy:

  • MISRA C WG to publish a simple whitepaper containing a simple applicability matrix of the C rules, unedited from the C document, that we believe "can be" applied to Rust (so, not a freestanding document, just listing which ones have any application at all);

  • the Guidelines Subcommittee to take authorial stewardship of the Iron Carbide rules, (which are the IP-neutral form of the applicable MISRA rules, plus the absolute bare minimum of new rules to fill in the gaps left by dropping inapplicable C rules) and be able to provide review and then a publication authority;

  • at some point in the future after it passes review by the SCRC, MISRA might pick up Iron Carbide and stamp it with the red triangle of approval (but probably not claim authorial ownership of it anymore at that point).

@PLeVasseur
Copy link
Collaborator Author

FYI @AlexCeleste -- I've put space on the agenda to bring the general concept back in next week as the discussion seemed to be taking off. No pressure to have everything drafted up for next time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
coding guidelines Related to work in the Coding Guidelines Subcommittee
Development

No branches or pull requests

3 participants