Repository navigation
Support #![no_std] without liballoc #58
Description
Activity
- added a commit that references this issue
on May 21, 2020 tinyvec is necessary because theoretically decompositions and compositions can map to an unbounded number of decomposed # code points. There's probably a small practical limit in what the composition data allows though
There's probably a small practical limit in what the composition data allows though
Perhaps
tinyvec::ArrayVeccould work? (or could be used onno_stdw\oallocat least)Sure, PRs welcome. Ideally something that switches between arrayvec and a non panicky variant
Reacted by Tony Arcieri...arrayvec and a non panicky variant
Oh, now I see
ArrayVecdoesn't have any fallible APIs and always panics on overflow. That's not great.Elsewhere I use
heapless::Vecwhich does provide fallible APIs, and a trait like this to abstract overheapless::Vecand heap-based data structures (really wish something like this were incore):https://docs.rs/veriform/0.1.0/veriform/derive_helpers/trait.TryExtend.html
I'd like to be able to use
is_nfc_quick()/is_nfd_quick()in a context where liballoc isn't available.It looks like the only thing linking
liballocright now istinyvec. Would it be possible to maketinyvecinto an optional dependency?