Rust SIG meeting 2025-09-02 #9
darkwisebear
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Attendees
@PLeVasseur 🦀💬
Naveen Ravi 🚶
Elena Gantner 🦀🚗 (Notetaker)
Vamsi Peddina 🦀
Rama
@darkwisebear
Kalidas Rajendran
Agenda
Issues
Discussions are now active!
Tasks
Minutes
Pete: offer to share different knowledge bases we as rust-sig have knowledge of (for link see agenda point 5.b).
To join the consortium (or subcommittees) the issues in the safety-critical consortium repo can be used
S-Core could also be a good resource for rust in automotive context. Markus gives a short info about the goals there with rust. See agenda point 5.c.ii for an example of an api there
Markus notes that diagnosis solution for score will be using opensovd
Markus: no - the interface is defined in c++ and macros will translate the interface to rust. Bindings from c++ to rust are still generated by hand. Markus notes that in the target solution this should be automatic and not ‘'visible’' to the users. An example can be found at the link in agenda 5.c.iii
Pete: there is some initial support from Electrobit and Vector for rust on µcontrollers
Vamsi notes that there are some production ECUs fully in rust.
Markus: is this ECU safety related?
Vamsi: the ECU is power related, so it should be safety related context.
Rama: at the moment Rust is still quite far away from production use in their company.
Coding guidelines from the safety-critical rust consortium come into play here to support the safety certification process
Beta Was this translation helpful? Give feedback.
All reactions