Skip to content

Latest commit

 

History

History
107 lines (87 loc) · 7.49 KB

File metadata and controls

107 lines (87 loc) · 7.49 KB

Coding Guidelines Subcommittee Meeting on 2026-06-10 @ 1600 CEST / 1100 EDT

Link to meeting time in common time zones.

Search Key Description
todo Action Item
decision Something decided on
important Key information

Agenda

  1. Solicitation of notetaker
  2. Acceptance of Previous Meeting Minutes
  3. Introduction of new members
  4. The SEI CERT Coding Standard for Fortran (David)
  1. Coverage of MISRA C and CERT C in 2026 (Félix / Markus updates)
  1. 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
  1. Round table

Check-in area

  • David Svoboda (-:
  • Max Jacinto 📚
  • Kaneko Satoshi 🫥
  • Mira Baumann
  • Pete LeVasseur 💯
  • Oreste Bernardi 🧠
  • Markus Hosch

Notetaker:

  • David Svoboda

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

Housekeeping section

Tasks

  • xx

Meeting Minutes

  • Acceptance of Previous Meeting Minutes: Accepted
  • Introduction of new members
  • The SEI CERT Coding Standard for Fortran (David)
  • Read more here: https://www.sei.cmu.edu/blog/the-sei-cert-coding-standard-for-fortran/
  • Standards published for almost 20 years 🎉
  • Fortran is new and still has some areas of improvement
    1. Rules: What to follow that are specific and should be followed
    2. Recommendations: Things you can violate if you’re careful
  • TYP02-F. Prohibit implicit typing in all program units
    1. Kind of odd; don’t have to declare before usage
    2. If you just start using a variable, the letter that this variable name begins with determines its type
    3. Recommended to, for all variables explicitly declare types of them
  • CERT C has on the order of ~200+ total rules and recommendations, so call to action for if anyone else would like
  1. Coverage of MISRA C and CERT C in 2026 (Félix / Markus updates)
  1. 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
  • Mira: Most missing stuff is about inheritance. Would like review. Also lots of items about the standard library.
  • David: Difficult because MISRA C++ is not free.
  • Mira: Yes. I had to buy it.
  • Markus: Applicability of inheritance to Rust. Traits do have inheritance.
  • Mira: MISRA C++ was mostly about virtual inheritance. Also it has very little rules about templates.
  • Markus: It is good to think about how rules would apply in alternate technologies.
  • Pete: I have enlisted a MISRA C++ member to help out.
  1. Review batches for CERT C Rust Mapping (Pete) (tabled)
  2. Round table

Material

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

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