We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Methods on Vec are not available even if Vec is in the prelude;
let v: Vec<i32> = Vec::new(); Vec::len(&v); // (a) -> error: unresolved name `Vec::len` std::vec::Vec::len(&v); // (b) -> OK!
fix: use std::vec::Vec; and both lines (a) and (b) compile!
use std::vec::Vec;
BitvSet is just weird and doesn't ever cooperate:
BitvSet
use std::collections::BitvSet; let bs = BitvSet::new(); BitvSet::len(&bs); // error: unresolved name `BitvSet::len`
use was fine with Vec -- but not this time.
use
And this is weirder:
extern crate collections; use std::collections::BitvSet; fn main() { let bs = BitvSet::new(); BitvSet::len(&bs); // error: unresolved name `BitvSet::len` std::collections::BitvSet::len(&bs); // error: unresolved name `std::collections::BitvSet::len` collections::bitv_set::BitvSet::len(&bs); // error: unresolved name `collections::bitv_set::BitvSet::len` collections::bit::BitvSet::len(&bs); // error: function `len` is private }
UFCS tracking issue: #16293
The text was updated successfully, but these errors were encountered:
These are resolved.
Sorry, something went wrong.
No branches or pull requests
Methods on Vec are not available even if Vec is in the prelude;
fix:
use std::vec::Vec;
and both lines (a) and (b) compile!BitvSet
is just weird and doesn't ever cooperate:use
was fine with Vec -- but not this time.And this is weirder:
UFCS tracking issue: #16293
The text was updated successfully, but these errors were encountered: