Skip to content
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

der: deprecate TagNumber::new #1727

Merged
merged 1 commit into from
Mar 18, 2025
Merged

Conversation

tarcieri
Copy link
Member

After #1651 the inner u32 of TagNumber is now pub and the TagNumber::new function no longer maintains an invariant (which it previously did by panicking when tag numbers are out-of-range).

With the field now pub there is no longer a need to call a function to construct a TagNumber, instead it can be done directly.

@baloo
Copy link
Member

baloo commented Mar 18, 2025

you'll need to exclude changes made to spki, x509-cert and all other crates currently excluded from the workspace.
We can bring those back in when #1689 merges (or I can push a revert of that over there)

@tarcieri tarcieri force-pushed the der/deprecate-tag-number-new branch from 851824f to e814957 Compare March 18, 2025 20:13
After #1651 the inner `u32` of `TagNumber` is now `pub` and the
`TagNumber::new` function no longer maintains an invariant (which it
previously did by panicking when tag numbers are out-of-range).

With the field now `pub` there is no longer a need to call a function to
construct a `TagNumber`, instead it can be done directly.
@tarcieri tarcieri force-pushed the der/deprecate-tag-number-new branch from e814957 to d6c2943 Compare March 18, 2025 20:15
@tarcieri tarcieri merged commit 93c8be8 into master Mar 18, 2025
107 checks passed
@tarcieri tarcieri deleted the der/deprecate-tag-number-new branch March 18, 2025 20:36
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