Coding Guidelines Subcommittee Meeting on 2026-07-15 @ 1600 CEST / 1100 EDT

Link to meeting time in common time zones.

Agenda

Solicitation of notetaker
Acceptance of Previous Meeting Minutes
Introduction of new members
Interest in the MISRA C++ mapping (mira / Pete)
- Updates on new things in the MISRA C++ => Rust mapping
- In talks with MISRA folks still; but in practice the procedure outlined seemed reasonable to them
- Please register interest on this Zulip thread
Working session: review feedback on the CERT C to Rust coding guidelines mapping
- Parent tracking issue: #336 Mapping of CERT C to Rust Guidelines
- Review batches: 1/5, 2/5, 3/5, 4/5, and 5/5
  - The 2/5 batch has the most as-yet unreviewed mappings, but some others have them here or there too.
- Goal: work through review feedback, confirm or revise the proposed Rust categorization, and capture decisions and follow-up work in the relevant issues
- Group A - first 7 rules from 2/5
  - https://meet.google.com/muk-bsjv-oke
  - Group:
    1.
- Group B - 4 last rules from 2/5 and 4/5
  - https://meet.google.com/svx-rtsv-izb
  - Group:
    1.
Round table

Notetaker:

For tips on how we take notes in the Safety-Critical Rust Consortium, please see the Meeting Notetaker Role doc.

Meeting minutes were accepted with no objections
No new members on the call
Mira reported that there are four items left for grab on MISRA C++ mappings
One group will go for the first seven rules of 2/5, the other group for the last four of 2/5 and all three in ⅘
- The second group was unable to join the sub-meeting without invitation from the organizer, so the group returned to the main meeting for the discussion
Subgroups returned to the main meeting.
- Group 2 will create an issue with their comments which then can be linked from the review issue.
- Group 1: FIO39 is more unclear on how it is actually implemented in Rust
  - https://doc.rust-lang.org/std/io/index.html#io-safety - it feels like this might need some rule about file I/O
  - New issue Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines#428 (comment)
Roundtable:
- Do we want to recommend the format for justification for required rules?
  - MISRA 2020 has guidance on these
  - Standardizing on the existence of a reason field for required rules feels like consensus, but the contents of the field are left to the implementer

Any material to read before the meeting should be included here.

Overview of Safety-Critical Rust Rust Project Goals Roadmap (Pete)

Soliciting those interested in Normative Documentation for Sound unsafe Rust goal
- Register interest here on Rust Zulip
Soliciting those interested in Establish a Spot for Safety-Critical Lints in Clippy goal
- Register interest here on Rust Zulip