-
Notifications
You must be signed in to change notification settings - Fork 117
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
Undocumented Cargo.toml features #194
Comments
You are right about lack of enough documentation (btw - we gladly accept PRs, including for documentation!). Yet, you are also asking a generic Rust "what is the difference between If you are opting out from This old Rust bug is containing a nice and more elaborated info on the generic question you are asking: rust-lang/rust#66740 |
You are right that I'm new to embedded and no-std rust (though I have done that sort of things in C before). In the case of the HALs and related crates it wasn't clear to me where they are 1) enabling feature that use alloc/std 2) providing things that allow std/alloc to work. 3) providing things that allow non-std to work (i.e. replace things that std/alloc would normally provide). |
The README only documents a handful of the features (native, pio, binstart and libstart). However, there are several more:
While I can guess roughly about what these do, it would be nice to have documentation on them. For example, should I use alloc_handler here or the alloc feature in esp-idf-svc? What is the difference?
The text was updated successfully, but these errors were encountered: