You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Therefore, we should suggest something else. Maybe we should also change the signature of multicore::Core::spawn to take a pointer instead of a &'static mut for the stack?
The text was updated successfully, but these errors were encountered:
Both in our docs and in some examples, we suggest using a
static mut
for allocating memory for core1's stack:With rust 1.83, this will cause a warning (at least it does with current beta), and with edition 2024 the lint will become deny-by-default. (https://doc.rust-lang.org/nightly/edition-guide/rust-2024/static-mut-references.html)
Therefore, we should suggest something else. Maybe we should also change the signature of
multicore::Core::spawn
to take a pointer instead of a&'static mut
for the stack?The text was updated successfully, but these errors were encountered: