-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
feature request: add convenient [] operator to std::vec::Vec #13031
Comments
Ok, thanks for clarification. |
I don't think we need this as another issue. I've already mentioned this in #11875. |
Dear Developers, |
@huonw Thanks a lot for clarification! |
fix: resolve associated types of bare dyn types Fixes rust-lang#13031 We've been dropping the associated type bindings of trait object types that were written without the `dyn` keyword. This patch reuses the lowering logic for `TypeRef::DynTrait` so the associated type bindings are properly lowered.
Dear Developers,
Rust language occurred to be amazingly suitable for many programming tasks.
For example, I successfully completed in Rust Coursera Illinois VLSI CAD: Logic to Layout one of the programming assignments and going to use Rust for the others.
Unfortunately after recent changes to the language the Rust code for the completed assignment occurred to be broken. No problem with it as the language evolves.
But the following constructs proposed for the new
vec_ng::Vec design
(below)v.get(1)
and especially*v.get_mut(1)
instead of used to be[]
are bulky and over-complicated in my opinion:Could you please add more usual
[]
index access tostd::vec_ng::Vec
design?Thanks!
The text was updated successfully, but these errors were encountered: