-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Rust-analyzer depends on anymap 1.0.0-beta.2 #15500
Comments
Looks like the soundness issue was fixed in the version we're using. It might be nice to move off |
We should move off of it I think, it's easy enough to self implement this, especially since we don't need the entire API surface either |
Hi, can I try to work on this issue? |
@shogo-nakano-desu go ahead! |
internal: port anymap ## Description - The anymap crate has been ported. During this process, unnecessary features for rust-analyzer have been removed. - From the tests that were checking the existing licenses, the anymap license (`BlueOak-1.0.0 OR MIT OR Apache-2.0`) has been removed. ## Requests - While porting the code this time, I have tried to respect the original author's intentions and have kept the comments/codes as much as possible. Please don't hesitate to tell me if you think the comments/codes also need to be appropriately modified. - If there are any necessary changes regarding the licensing or anything else, please let me know so I can fix them. ## Issue #15500
Port added in #15618. Now we're not going to know about any |
This appears to be unmaintained and contain soundness issues: https://rustsec.org/advisories/RUSTSEC-2021-0065.html.
See also chris-morgan/anymap#37
The text was updated successfully, but these errors were encountered: