Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd no_std support #49
Conversation
|
Usually crates define a |
|
Or maybe I dreamt that... I was pretty sure it was the case for |
|
Sure, I can do that too. Some crates follow that convention, but some others don't (like |
|
Following |
est31
commented
May 20, 2017
|
no_std is an anti pattern, see rust-lang/rfcs#1841 (The RFC itself is being rejected, but it stays an antipattern). |
|
I think Unfortunately we delayed long enough that the |
|
@bors-servo r+ Since the move to |
|
|
Add no_std support This library can easily support `no_std` code on `nightly`; it does require the `collections` feature, however. This PR adds support for this feature by enabling a on-by-default `std` feature. This feature can be turned off to support `no_std` mode. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/rust-smallvec/49) <!-- Reviewable:end -->
|
The other thing is that I believe that the collections crate still exists; now it's just a wrapper around |
|
|
Document and test no_std support This builds on the new "std" Cargo feature added in #49. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/rust-smallvec/53) <!-- Reviewable:end -->
Pratyush commentedMay 20, 2017
•
edited by larsbergstrom
This library can easily support
no_stdcode onnightly; it does require thecollectionsfeature, however. This PR adds support for this feature by enabling a on-by-defaultstdfeature. This feature can be turned off to supportno_stdmode.This change is