-
Notifications
You must be signed in to change notification settings - Fork 65
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
Serde crate showing question mark #137
Labels
enhancement
New feature or request
Comments
Thanks for the report! This could be related to #116 |
Looking at serde 1.0.117 -
Yes we will have to manage test suite / dev dep handling differently. Just curiosity wise as well unrelated to this error - serde has unsafe as of now
Action(s) To Resolve The Issue
|
This was referenced Jan 6, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
i just have installed
cargo-geiger
to see, which of my dependencies contain unsafe code and I found the serde crate (1.0.117) with a question mark, although it contains#[forbid(unsafe_code)]
(see https://github.com/serde-rs/serde/blob/master/serde/src/lib.rs#L139).I am not sure if this was already reported. Please close this if this is a duplicate..
Best regards,
Maximilian
The text was updated successfully, but these errors were encountered: