Open
0 of 3 issues completed
Description
General discussion / notes / thoughts about stabilizing heapless with a 1.0 release.
Checklist
- Review issues in the v1.0.0 milestone
- Planned breaking changes are tracked in Tracking issue for planned breaking changes: #494
- Review Rust API Guidelines Checklist
- Review allowed warnings and clippy lints
- Review non-default clippy lints (
-W clippy::pedantic -W clippy::nursery) - Review public enums and structs, should any be marked
#[non_exhaustive]? - Review explicit panics, unwraps, expects in non-test code
- Review crate features
- grep for
fixme,todo, ect. - Review open issues
- Review open pull-requests
- When 1.0 looks ready engage with community, solicit feedback
- Announce in rust-embedded WG meeting
- Announce in this issue
- Anywhere else?
Dependencies
- defmt will reach 1.0 soon: https://ferrous-systems.com/blog/defmt-1-0/
- ufmt may not be 1.0, leave as-is and document it will not be covered by semver?
- hash32 needs a 1.0, roadmap to v1.0.0? rust-embedded-community/hash32#17
Questions
- What should the MSRV policy look like?
- I think Ferrocene support is important for some users, this is currently at 1.83.0