-
Notifications
You must be signed in to change notification settings - Fork 13.4k
regression: alloc::prelude removed #90322
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
I think we likely want to just close this but wanted to file it for awareness, but I don't expect even a relnotes inclusion since it's a pretty clear use of an unstable feature. |
How many crates are affected? |
1 -- with the usual caveat of "that Crater detected". But I expect breakage to be minimal, and the migration to a stable path for any affected uses should be fairly easy. |
Given that this is only a single known crate with 90 all-time downloads, I'm inclined to close this as well. Unstable APIs are unstable for a reason. That said, what can be done about this stability hole? I just checked the source code for the crate and it doesn't do anything out of the ordinary. Is there documentation of this bug somewhere? |
It's #15702 |
Wow, that's an old issue. |
Closing this, as the impact seems very minimal. A solution for #15702 would be nice. |
no-proto is also broken, cc @only-cliches -- discovered in the rustdoc crater run. |
Uh oh!
There was an error while loading. Please reload this page.
#89898 removed alloc::prelude, which was unstable, but some crates depended on it with absolute paths (which is a known stability hole):
The text was updated successfully, but these errors were encountered: