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
In this section we cover how to get data structures like std::Vec and std::String working in #[no_std] applications. There are two ways: (a) using the alloc crate, #[global_allocator] and #[alloc_error] -- heap allocated collections -- and (b) using the heapless crate -- fixed capacity collections. There should be a subsection that covers the advantages and disadvantages of using one or the other.
Triage: a draft for this section (renamed to collections) has landed. What's left to be done here is decide if we want to add more content to this section.
I think it may make sense to talk about &'static mut T, which is the no-allocator version of Box<T>, in this section. Both are pointer sized (thus cheap to move around) and own the value behind the pointer (&'static mut has move semantics).
We will land additional content (e.g. &'static mut T) in the unsorted section and later on decide whether to merge it with collections or put in a separate section. Closing this issue as done.
From @japaric on July 17, 2018 14:37
In this section we cover how to get data structures like std::Vec and std::String working in #[no_std] applications. There are two ways: (a) using the alloc crate, #[global_allocator] and #[alloc_error] -- heap allocated collections -- and (b) using the heapless crate -- fixed capacity collections. There should be a subsection that covers the advantages and disadvantages of using one or the other.
Copied from original issue: rust-embedded/wg#125
The text was updated successfully, but these errors were encountered: