Skip to content

Heapless 1.0 #535

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

Open
14 tasks
newAM opened this issue Mar 9, 2025 · 4 comments
Open
14 tasks

Heapless 1.0 #535

newAM opened this issue Mar 9, 2025 · 4 comments
Milestone

Comments

@newAM
Copy link
Member

newAM commented Mar 9, 2025

General discussion / notes / thoughts about stabilizing heapless with a 1.0 release.

Checklist

Dependencies

Questions

  • What should the MSRV policy look like?
    • I think Ferrocene support is important for some users, this is currently at 1.83.0
@newAM newAM added this to the v1.0.0 milestone Mar 9, 2025
@rursprung
Copy link

see also the discussion on #410 - i think you wanted to push hash32 to 1.0 first (rust-embedded-community/hash32#17)?

@newAM
Copy link
Member Author

newAM commented Mar 24, 2025

Whoops I forgot #410 existed, sorry about that!

@reitermarkus
Copy link
Member

reitermarkus commented Apr 3, 2025

Got some more issues:

  • Remove Q* type aliases for MpMcQueue, and rename it to just Queue to align with spsc::Queue.
  • Don't export indexmap types at the top-level, except indexmap::IndexMap itself. Also, should the module be called index_map instead? Same for indexset module and IndexSet types.
  • Align histbuf module and HistoryBuffer type name as history_buf and HistoryBuf?

@pvdrz pvdrz mentioned this issue Apr 4, 2025
@pvdrz
Copy link
Contributor

pvdrz commented Apr 4, 2025

Got some more issues

addressed in #547

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants