Skip to content

Conversation

@tarcieri
Copy link
Member

@tarcieri tarcieri commented Jun 2, 2025

AeadInPlace was removed in #1798, however in migrating some older code I thought it would be really helpful to have backwards compatibility and deprecations in place to help people migrate to the new names, especially as the "in place" -> "inout" migrations aren't entirely intuitive.

`AeadInPlace` was removed in #1798, however in migrating some older code
I thought it would be really helpful to have backwards compatibility and
deprecations in place to help people migrate to the new names,
especially as the "in place" -> "inout" migrations aren't entirely
intuitive.
@tarcieri tarcieri requested a review from newpavlov June 2, 2025 12:42
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.

Personally, I am not a fan of having deprecated items in a new breaking release, but I guess it could help users with gradual migration.

@tarcieri
Copy link
Member Author

tarcieri commented Jun 2, 2025

These migrations are just so much easier when your code still compiles but you get helpful warnings about what needs to be changed and where, instead of compile errors and having to look through crate-by-crate changelogs

@tarcieri tarcieri merged commit cac73b0 into master Jun 2, 2025
10 checks passed
@tarcieri tarcieri deleted the aead/aead-in-place-deprecation branch June 2, 2025 12:50
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