-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the scope of no_std support? #467
Comments
As far as I understand it |
Oh, any technical reason for that? |
Yes, From anyhow's README (emphasis mine):
So anyhow works with Footnotes
|
I have |
I'm aware 😄. It's just that most of my embedded usage / knowledge of usage has been places with no allocation capability (e.g. tiny devices, Windows kernel drivers). In addition, I don't like using Anyway, can you try this branch and see if it works for your case? https://github.com/shepmaster/snafu/tree/alloc That should look something like this in your Cargo.toml: [dependencies.snafu]
default-features = false
features = ["rust_1_81", "alloc"]
git = "https://github.com/shepmaster/snafu"
branch = "alloc" |
I'm trying to use Snafu in a no_std environment, and the basic example from the docs doesn't work.
It can't find
Whatever
and I checked the sourced and it's behindstd
feature.So what is the scope of support for
no_std
?The text was updated successfully, but these errors were encountered: