Johnathan Van Why
Johnathan Van Why
The stabilization PR for `feature(const_fn_trait_bound)` was merged: https://github.com/rust-lang/rust/pull/93827#event-6197814397. Unless it is reverted, `feature(const_fn_trait_bound)` will be stable in 1.61.0.
One other reason we discussed for releasing 2.1 now is that `libtock-rs` is unsound on Tock 2.0, and releasing 2.1 would allow us to say "`libtock-rs` works on a stable...
The CI failure appears to be unrelated to this PR.
I have no opinion on deleting vs. supporting TMP006, but I wanted to chime in on this point: > If we do want to keep the driver, just having a...
If the Tock kernel does not run code in interrupt context, and will remain single-threaded, then we could use normal (non-`mut`) `static` declarations as well. I think a `TockStatic` type...
I agree this is a soundness issue, and that the fix is to store the slice as a raw pointer and length.
> Our data structures are not (and should not) be `Sync`. If there was a way for us to mark something as unsafe to access from a global (the way...
Updating `rustup` isn't the only problem. The current `ubuntu-latest` version -- 20201129.1 -- already has `rustup` 1.23.0 (I don't know if it's at 100% deployment yet), yet I received the...
@hudson-ayers Is there prior art here in the Tock project? I suspect there is.
I am supportive of using Cargo features to control how much code libtock-rs includes to limit bloat. I'd rather not condition this on debug/release mode, as it is a breaking...