Skip to content

dbl v0.4.0 #1194

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

Merged
merged 2 commits into from
Aug 6, 2025
Merged

dbl v0.4.0 #1194

merged 2 commits into from
Aug 6, 2025

Conversation

tarcieri
Copy link
Member

@tarcieri tarcieri commented Aug 4, 2025

Changed

  • Migrated from generic-array to hybrid-array (#944)
  • Edition changed to 2024 and MSRV bumped to 1.85 (#1149)
  • Seal the Dbl trait (#1198)

Closes #1077

@tarcieri tarcieri requested a review from newpavlov August 4, 2025 21:27
Copy link
Member

@newpavlov newpavlov left a comment

Choose a reason for hiding this comment

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

I have left some concerns here, but it's not a blocker and I am fine with merging it as-is.

@tarcieri
Copy link
Member Author

tarcieri commented Aug 5, 2025

I think we should release it, but as noted in #1077 we can also continue working on a replacement in parallel, and it's easy to replace

@newpavlov
Copy link
Member

I think we can move forward with this after rebase (don't forget to update the release date and changelog in OP).

@tarcieri tarcieri merged commit 8a58487 into master Aug 6, 2025
101 checks passed
@tarcieri tarcieri deleted the dbl/v0.4.0 branch August 6, 2025 13:49
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.

dbl: retire crate and vendor implementation into downstream users?
2 participants