A State of the Field Report on Rust Guidelines and Standards

“The Rust programming languages is an exciting alternative to C and C++ for its built-in memory-safety management. This is a huge advantage for safety-critical industries; however, there are not yet any coding standards specifically for Rust. That’s about to change: Multiple projects are already underway to bring Rust into alignment with the requirements of safety-critical development.”

, Perforce, webinar overview

What’s covered

The session is a state-of-the-field report on the standards and guidelines work that is bringing Rust into safety-critical development. Three threads are converging:

• Three major Rust guidelines projects that are working toward near-term public release.
• Language specification through “FLS” and ISO recognition via WG23: the formal-language and standardisation paths Rust needs to be taken seriously by safety-critical regulators.
• Collaboration with the C++ and MISRA communities: Rust isn’t being defined in isolation; the lessons from MISRA C, MISRA C++, and the C++ Core Guidelines feed into what Rust guidelines need to look like.

The discussion covers work emerging from the Safety-Critical Rust Consortium, the ISO/IEC JTC 1/SC 22 WG23 track, and the in-flight cross-community effort with MISRA and C++ working groups. Bring your questions, the session ends with live Q&A.

Speaker

Session times

Two regional broadcasts on the same day:

Region	Time
India (live with EMEA)	Wednesday 3 June 2026, 14:30 IST
EMEA (UK)	Wednesday 3 June 2026, 10:00 BST
US Central	Wednesday 3 June 2026, 12:00 CDT
US East	Wednesday 3 June 2026, 13:00 EDT
US West	Wednesday 3 June 2026, 10:00 PDT

Registration and attendance is completely free. Indian engineering teams are best served by the EMEA broadcast at 14:30 IST. Times sourced from the official Perforce webinar page.

Why Indian teams should care

Rust adoption in Indian safety-critical programs, automotive ECUs, medical devices, railway signalling, defence avionics, has stalled at the same point in every project: “we love the memory safety, but our regulator wants a coding standard and there isn’t one yet.” The webinar is a credible read on how soon “there isn’t one yet” stops being true, which projects to track, and what the eventual standards landscape will look like for Rust the way MISRA C looks for C today.

For teams already evaluating Rust in mixed-language codebases, the same Rust analysis support landed in Helix QAC and Klocwork 2026.1 earlier this year, which means the static-analysis tooling story is now ahead of the standards story, and both are moving fast.

Why GSAS is sharing this

GSAS Micro Systems is the authorized India partner for Perforce Helix QAC and Perforce Klocwork. We’re resharing this webinar so Indian teams running Helix QAC or Klocwork, or evaluating them for the first time as part of a Rust-to-safety-critical roadmap, hear the standards-progress update directly from the Perforce engineer working on the Rust analyzer.

If your team is sizing a Rust adoption decision against your safety case, or you have questions about how the in-flight Rust standards work changes the buy/wait calculus on Klocwork or QAC for India-based projects, talk to us after the webinar.

Reserve your seat on perforce.com →