2 ms·
This is almost all astonishingly sensible. If static provisioning works at all for the application, it is obviously better. If you did have a need to have dyna
by ncmncm 5y ago
This is almost all astonishingly sensible. If static provisioning works at all for the application, it is obviously better.
If you did have a need to have dynamic tasks -- e.g., drivers for an unbounded set of USB peripherals -- one of the static tasks could be the executive for those. They would still be unable to interfere with the other, static tasks.
I have to agree with the rabbi that the Rust evangelism detracts from the talk. E.g., the runtime borrow checking example, which does not rely on any Rust mechanism, would work as well with any language.