-
Notifications
You must be signed in to change notification settings - Fork 172
der: introduce an AnyLike trait to mark parameters
#1415
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
Conversation
spki/src/lib.rs
Outdated
| //! let alg_id = AlgorithmIdentifier { | ||
| //! oid: alg_oid, | ||
| //! parameters: Some(params_oid) | ||
| //! parameters: Some(Any::encode_from(¶ms_oid).unwrap()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this was a regression introduced in #769
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How is this a regression? The change seems like a regression.
|
Last set of CI errors are related to #799 I think. |
|
I'm not sure I understand the purpose of this trait or why you're adding bounds for it, nearly all of which seem unused?
...but |
|
I guess your goal here is to try to constrain the parameters specifically to the ...but that seems needlessly restrictive. The ASN.1 concept of Is there a specific motivation for this change? |
|
Notably this precludes using e.g. |
|
The motivation was to compare the parameter to |
This newly defined
AnyLiketrait would help to make sure the parameters ofspki::AlgorithmIdentifierare serialized as Any.