-
Notifications
You must be signed in to change notification settings - Fork 227
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
Alter stability note in README and briefly explain unstable feature #2894
Conversation
README.md
Outdated
@@ -20,7 +20,7 @@ If you have any questions, comments, or concerns, please [open an issue], [start | |||
|
|||
> [!NOTE] | |||
> | |||
> This project is still in the relatively early stages of development, and as such there should be no expectation of API stability. A significant number of peripherals currently have drivers implemented but have varying levels of functionality. For most tasks, this should be usable already, however some more advanced or uncommon features may not yet be implemented. | |||
> This project is still in the relatively early stages of development. A significant number of peripherals currently have drivers implemented but have varying levels of functionality. For most tasks, this should be usable already, however some more advanced or uncommon features may not yet be implemented. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this paragraph is a left-over from the time this repo contained only the HAL - we probably should mentioin that crates in this repo come with different stability guarantees and are at different stages of maturity
esp-hal/README.md
Outdated
@@ -46,6 +46,12 @@ For help getting started with this HAL, please refer to [The Rust on ESP Book] a | |||
[s2-trm]: https://www.espressif.com/sites/default/files/documentation/esp32-s2_technical_reference_manual_en.pdf | |||
[s3-trm]: https://www.espressif.com/sites/default/files/documentation/esp32-s3_technical_reference_manual_en.pdf | |||
|
|||
## `unstable` feature | |||
|
|||
We aim to avoid enabling experimental features automatically. Allowing automatic access could result in users unintentionally utilizing APIs that are still under development. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is very brief and fuzzy at the same time - we should mention that the stable feature set is ... stable - and other parts guarded by the unstable feature will likely see breaking changes .... something like that
I don't think we need to explain here why we don't enable unstable by default 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Not sure if this isn't too brief 😅
closes #2501