3 ms·
For embedded code, I'd recommend that all application code should be compiled with the `--deny unsafe-code` option. Then the compiler will stop you. A separate
by jononor 10y ago
For embedded code, I'd recommend that all application code should be compiled with the `--deny unsafe-code` option. Then the compiler will stop you.
A separate module for the I/O code providing is the only place where one should use `unsafe`. Extra care must be taken here, in code review and in testing.
- milesrout 10y agoDo you have any idea how impossible it is to do anything useful without unsafe in Rust on a microcontroller?
- pjmlp 10y agoIf Ada, Pascal and Basic can, so can Rust. Every case where this is not true is a bug.
- jononor 10y agoAbout as hard as on desktop? I mean, many of the core datastructures commonly used there are implemented using unsafe. This does not mean that the application code must or should be riddled with unsafe code blocks... For a very simple example see https://github.com/hackndev/zinc/blob/master/examples/blink_stm32f4/src/main.rs https://github.com/hackndev/zinc/blob/master/examples/blink_...