Hey folks 👋 the survey closes tomorrow, so be sure to get your thoughts in regarding "what it would take" to make Rust more suitable to your safety-critical industry and business!

Did you know that the Tooling Subcommittee has put together a process for submitting tools which are or potentially could be used for safety-critical systems development in Rust?

More details follow

Now that we've gotten each guideline into its own source file to help with reducing merge conflicts, should we:
1. have the rendered version as it is today, with all guidelines in a chapter?
2. have the rendered version with a flat list in the chapter, linking out to one guideline per rendered page?

We've improved the guidance on how to use the coding guideline that's been converted from Markdown to reStructuredText and -- we now test all code examples in the submitted guideline!

More details follow.

A couple of significant upgrades to contributing to our coding guidelines:
- all example code is now extracted and tested
- each guideline exists as its own source file

These both fall under our contributor experience label and we take these seriously.

Writing a bit more about this below

Howdy y'all 👋 reminder that our survey of safety-critical Rust users for potential Project Goals in 2026 ends next Friday

Check the quoted post for more details!

bsky.app/profile/safe...

Are you in a safety-critical industry? Using the Rust programming language (@rust-lang.org) or would like to? Make your voice heard when it comes to what you'd like to see for Rust Project Goals!

(survey link below)

Hey there 👋 are you aware of the Safety-Critical Rust Consortium? 🦀🦺

We were founded about a year and a half ago with the mission to make Rust a first-class choice when starting a safety-critical systems project (think trains, planes and automobiles -- and more).