std feature (by default) and compiling for no-std #3
Conversation
|
Please let me know if I should add a changelog item to this as well. |
|
Hi! This is great, and something I've been wanting to include for some time. Thanks so much for writing it! I'm going to accept it as-is, and then add more distinction between: neither alloc nor std, alloc but not std, both alloc and std. The end result, when I publish [dependencies.bitvec]
default-features = false
features = ["alloc"]no-alloc-no-std environments will have access to |
|
@myrrlyn Thanks for the quick turnaround! Having |
|
Commit 3fe2b56 adds the |
|
Seems to work. Thanks |
Recently I wanted to use a bitvec in WASM in a project of mine. This PR adds an
stdfeature which is enabled by default. When the feature is not enabled, the crate is compiled withno-stdand draws on thealloccrate for certain types and traits. This means that compiling this crate forno-stdcurrently requires a nightly compiler, although this is OK for my uses.The API when compiling with
stdis backwards-compatible with the previous state.