Skip to content

Upgrade all crates to the 2024 edition and bump MSRV to 1.85 - #472

Merged
newpavlov merged 9 commits into
RustCrypto:masterfrom
baloo:baloo/edition-2024
Feb 28, 2025
Merged

Upgrade all crates to the 2024 edition and bump MSRV to 1.85#472
newpavlov merged 9 commits into
RustCrypto:masterfrom
baloo:baloo/edition-2024

Conversation

@baloo

Copy link
Copy Markdown
Member

No description provided.

@baloobaloo changed the title Upgrade all crates to the edition2024 and bump MSRV to 1.85Upgrade all crates to the 2024 edition and bump MSRV to 1.85Feb 23, 2025
@baloo
balooforce-pushed the baloo/edition-2024 branch 2 times, most recently from d5fe39a to 7b79d26CompareFebruary 23, 2025 04:21
@baloo
balooforce-pushed the baloo/edition-2024 branch 3 times, most recently from e09b3dd to 66b672dCompareFebruary 23, 2025 05:07

@newpavlovnewpavlov left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

You also need to update hex-literal to v1.

Comment threadaes/src/armv8/encdec.rs Outdated
@baloo
balooforce-pushed the baloo/edition-2024 branch 2 times, most recently from 01ee216 to 7eb7c05CompareFebruary 23, 2025 05:57
Comment threadaes/src/lib.rs Outdated
)]
#![cfg_attr(docsrs, feature(doc_auto_cfg))]
#![warn(missing_docs, rust_2018_idioms)]
#![allow(unsafe_op_in_unsafe_fn)]

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I think it's better to do this allow on the per-module basis like I did in the hashes PR. With potential target_feature improvements (which would make some intrinsics safe inside functions with with enabled target features) we may enable this lint back.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

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

Ha, I've tried to read the patch for hashes, but github UI is very slow. I've thought you've used a big unsafe{ block, but that was only in sha1, I should have kept reading, my bad.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I did it in the initial commits, but then switched to #[allow(..)]. For example here I enable it for the function and here for the whole module.

@newpavlov
newpavlov merged commit 70fe50a into RustCrypto:masterFeb 28, 2025
@baloo
baloo deleted the baloo/edition-2024 branch February 28, 2025 03:23
@newpavlovnewpavlov mentioned this pull request Mar 2, 2026
newpavlov added a commit that referenced this pull request Apr 10, 2026
### Changed
- Bump `cipher` dependency to v0.5
- Edition changed to 2024 and MSRV bumped to 1.85 ([#472])
- Refactor ARMv8 `expand_key` ([#367])
- Added `#[inline]` attributes for `KeyInit::new` impls ([#386])
- Rework backends ([#442])
- Move `Block8` to the hazmat module ([#468])
- Relax MSRV policy and allow MSRV bumps in patch releases ([#477])
- Replace inline ASM with ARMv8 intrinsics ([#380])
- Enable ARMv8 backend by default ([#395])
[#367]: #367
[#380]: #380
[#386]: #386
[#395]: #395
[#442]: #442
[#468]: #468
[#472]: #472
[#477]: #477
newpavlov added a commit that referenced this pull request Apr 10, 2026
Most crates contain the following changelog entry:
### Changed
- Bump `cipher` dependency to v0.5
- Edition changed to 2024 and MSRV bumped to 1.85 ([#472])
- Relax MSRV policy and allow MSRV bumps in patch releases ([#477])
[#472]: #472
[#477]: #477
Sign up for freeto 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

@baloo@newpavlov