Skip to content

hash32: 0.3.0 -> 1.0.0#563

Draft
newAM wants to merge 1 commit intorust-embedded:mainfrom
newAM:hash32-1.0.0
Draft

hash32: 0.3.0 -> 1.0.0#563
newAM wants to merge 1 commit intorust-embedded:mainfrom
newAM:hash32-1.0.0

Conversation

@newAM
Copy link
Member

@newAM newAM commented Apr 26, 2025

hash32 1.0.0 is not out yet, this branch is for testing before the hash32 release.

See rust-embedded-community/hash32#17

@zeenix
Copy link
Contributor

zeenix commented Sep 3, 2025

hash32 1.0 was release a few months ago so that's not blocker anymore but this will be a breaking change so it has to be coordinated with all other breaking changes we'll want before 1.0.

@newAM
Copy link
Member Author

newAM commented Sep 3, 2025

Forgot I had this still open, I'll update it later today so it's ready to be merged for 1.0

@newAM newAM marked this pull request as ready for review September 3, 2025 23:42
Copy link
Contributor

@zeenix zeenix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@zeenix zeenix marked this pull request as draft September 4, 2025 10:19
@zeenix
Copy link
Contributor

zeenix commented Sep 4, 2025

@newAM Awesome! I converted to draft to avoid accidental merging. I hope you don't mind. :)

@amy-kwan
Copy link

Hi there! I opened a pull request recently to update the hash32 dependency, but closed it as I realized this PR already exists. I was wondering, are there any plans in merging this change in the near future?

For context, heapless on AIX currently brings in the byteorder crate (through hash32) in the dependency tree and we aren't able to build byteorder on AIX due to an assertion described in BurntSushi/byteorder#221.

@zeenix
Copy link
Contributor

zeenix commented Mar 12, 2026

I was wondering, are there any plans in merging this change in the near future?

Did you read the discussion above? There is a good reason it's in draft state.

@amy-kwan
Copy link

I was wondering, are there any plans in merging this change in the near future?

Did you read the discussion above? There is a good reason it's in draft state.

Thanks @zeenix - Yes, my apologies, I should rephrase my question. I was more so curious on the current state of things with respect to the other breaking changes and if we are getting to resolving those, which would affect when heapless v1.0 would be released.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants