Skip to content

update bytemuck version to match wide to avoid unnecessary extra versions#125

Merged
Lokathor merged 1 commit into
Lokathor:mainfrom
mcroomp:updatebytemuck
Dec 1, 2025
Merged

update bytemuck version to match wide to avoid unnecessary extra versions#125
Lokathor merged 1 commit into
Lokathor:mainfrom
mcroomp:updatebytemuck

Conversation

@mcroomp

@mcroomp mcroomp commented Dec 1, 2025

Copy link
Copy Markdown
Contributor

No description provided.

@Lokathor

Lokathor commented Dec 1, 2025

Copy link
Copy Markdown
Owner

Cargo should automatically combine all uses of bytemuck-1.y.z into a single crate version selection that both safe_arch and wide build against.

Can you demonstrate a situation where this does not happen?

@mcroomp

mcroomp commented Dec 1, 2025

Copy link
Copy Markdown
Contributor Author

Yeah you are right... now that you've update both safe_arch and wide to 1.0, I'm not getting the problem anymore. Not sure what was happening.

@Lokathor

Lokathor commented Dec 1, 2025

Copy link
Copy Markdown
Owner

I'm surprised it was happening previously, because the deciding factor should be the byremuck crate being 1.0, which it has been for years now.

Either way, there's no real harm in accepting this PR, so I'll merge it.

@Lokathor Lokathor merged commit 02296d1 into Lokathor:main Dec 1, 2025
12 checks passed
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.

2 participants