Feature request: no-std + alloc #121
Labels
Comments
|
Can you say specifically what features you need? And also why you can't enable std? |
|
Aye. Yes, this is definitely something we should do. I believe the only API that's added with (I don't think there is any |
BurntSushi
added a commit
that referenced
this issue
Jul 11, 2023
This crate currently only has a 'std' feature and of course support for no-std. But in that mode, it was also no-alloc. In practice, this crate is virtually all core-only, that is, no-std and no-alloc. There are really only a few parts that want std or alloc. For std, runtime CPU feature detection requires it. For alloc, there are a few minor APIs that require allocation. Previously, the only way to get the APIs that require allocation was to enable 'std'. This new feature permits getting those APIs without bringing in 'std'. I don't expect this to unlock any new or interesting use cases, but it will make downstream configurations a little more sensible and less annoying. Fixes #121
BurntSushi
added a commit
that referenced
this issue
Jul 11, 2023
This crate currently only has a 'std' feature and of course support for no-std. But in that mode, it was also no-alloc. In practice, this crate is virtually all core-only, that is, no-std and no-alloc. There are really only a few parts that want std or alloc. For std, runtime CPU feature detection requires it. For alloc, there are a few minor APIs that require allocation. Previously, the only way to get the APIs that require allocation was to enable 'std'. This new feature permits getting those APIs without bringing in 'std'. I don't expect this to unlock any new or interesting use cases, but it will make downstream configurations a little more sensible and less annoying. Fixes #121
BurntSushi
added a commit
that referenced
this issue
Jul 11, 2023
This crate currently only has a 'std' feature and of course support for no-std. But in that mode, it was also no-alloc. In practice, this crate is virtually all core-only, that is, no-std and no-alloc. There are really only a few parts that want std or alloc. For std, runtime CPU feature detection requires it. For alloc, there are a few minor APIs that require allocation. Previously, the only way to get the APIs that require allocation was to enable 'std'. This new feature permits getting those APIs without bringing in 'std'. I don't expect this to unlock any new or interesting use cases, but it will make downstream configurations a little more sensible and less annoying. Fixes #121
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was looking through the code of this crate. I have a need for something like this on a no-std + alloc target, but it seems several features (such as using
Cowfrom alloc) are missing. That should be possible to support.The text was updated successfully, but these errors were encountered: