-
Notifications
You must be signed in to change notification settings - Fork 138
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
Can't build arrayvec 0.7.5 - unresolved import std::path
(for no std)
#273
Comments
Thanks for reporting. Which rust platform and rust version? |
std::path
std::path
(for no std)
It fails for me on the latest Ubuntu runner by GitHub, for instance. |
std::path
(for no std)std::path
(for no std)
ok, it's no-std, I can see that now. It doesn't have a test in CI apparently. |
Will there be a 0.7.6 with this fix? Will 0.7.5 be yanked for being a breaking change for no_std users? |
0.7.6 is released now |
amazingly fast work. Thank you. |
Well, scary how fast multiple people noticed something broke. At least good that we now have CI coverage here for that facet (no-std).. |
Consider yourself a small, unpaid, peg in a very large stack. |
error[E0432]: unresolved import
std::path
--> C:\Users\evex.cargo\registry\src\index.crates.io-6f17d22bba15001f\arrayvec-0.7.5\src\array_string.rs:8:10
|
8 | use std::path::Path;
| ^^^^ could not find
path
instd
The text was updated successfully, but these errors were encountered: