Skip to content

Add vec::truncate, for efficiently shortening a vector. - #3301

Merged
catamorphism merged 1 commit into
rust-lang:incomingfrom
jld:vec-truncate
Aug 29, 2012
Merged

Add vec::truncate, for efficiently shortening a vector.#3301
catamorphism merged 1 commit into
rust-lang:incomingfrom
jld:vec-truncate

Conversation

@jld

@jldjld commented Aug 29, 2012

Copy link
Copy Markdown
Contributor

No description provided.

catamorphism added a commit that referenced this pull request Aug 29, 2012
Add vec::truncate, for efficiently shortening a vector.
@catamorphism
catamorphism merged commit ec9c68c into rust-lang:incomingAug 29, 2012
@catamorphism

Copy link
Copy Markdown
Contributor

Merged, thanks!

RalfJung pushed a commit to RalfJung/rust that referenced this pull request Feb 17, 2024
jaisnan pushed a commit to jaisnan/rust-dev that referenced this pull request Jul 29, 2024
Update Rust toolchain from nightly-2024-06-26 to nightly-2024-06-27
without any other source changes.
This is an automatically generated pull request. If any of the CI checks
fail, manual intervention is required. In such a case, review the
changes at https://github.com/rust-lang/rust from
rust-lang@fda509e
up to
rust-lang@4bc39f0.
U007D pushed a commit to U007D/rust-mos that referenced this pull request Aug 21, 2026
5935: Rewrite import insertion r=matklad a=Veykril
This is my attempt at refactoring the import insertion rust-lang#3947. I hope what I created here is somewhat in line with what was requested, it wouldn't surprise me .
`common_prefix` is a copy from `merge_imports.rs` so those should be unified somewhere, `try_merge_trees` is also copied from there but slighly modified to take the `MergeBehaviour` enum into account.
`MergeBehaviour` should in the end become a configuration option, and the order if `ImportGroup` probably as well?
I'm not too familiar with the assist stuff and the like which is why I dont know what i have to do with `insert_use_statement` and `find_insert_use_container` for now.
I will most likely add more test cases in the end as well as I currently only tried to hit every path in `find_insert_position`. Some of the merge tests also fail atm due to them not sorting what they insert. There is also this test case I'm not sure if we want to support it. I would assume we want to? https://github.com/rust-analyzer/rust-analyzer/pull/5935/files#diff-6923916dd8bdd2f1ab4b984adacd265fR540-R547
The entire module was rewritten so looking at the the file itself is probably better than looking at the diff.
Regarding the sub issues of rust-lang#3947:
- rust-lang#3301: This is fixed with the rewrite, what this implementation does is that it scans through the first occurence of groupings and picks the appropriate one out. This means the user can actually rearrange the groupings on a per file basis to their liking. If a group isnt being found it is inserted according to the `ImportGroup` variant order(Would be nice if this was configurable I imagine).
- rust-lang#3831: This should be fixed with the introduced `MergeBehaviour` enum and it's `Last` variant.
- rust-lang#3946: This should also be [fixed](https://github.com/rust-analyzer/rust-analyzer/pull/5935/files#diff-6923916dd8bdd2f1ab4b984adacd265fR87)
- rust-lang#5795: This is fixed in the sense that the grouping search picks the first group that is of the same kind as the import that is being added. So if there is a random import in the middle of the program it should only be considered if there is no group of the same kind in the file already present.
- the last point in the list I havent checked yet, tho I got the feeling that it's not gonna be too simple as that will require knowledge of whether in this example `ast` is a crate or the module that is already imported.
Co-authored-by: Lukas Wirth <lukastw97@gmail.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@jld@catamorphism@eholk