Replace truncate(0) with clear()#154029
Conversation
|
rust-analyzer is developed in its own repository. If possible, consider making this change to rust-lang/rust-analyzer instead. cc @rust-lang/rust-analyzer Some changes occurred in src/tools/compiletest cc @jieyouxu |
|
r? @joboet rustbot has assigned @joboet. Use Why was this reviewer chosen?The reviewer was selected based on:
|
There was a problem hiding this comment.
Please don't modify subtrees like rust-analyzer inside the rust-lang/rust repo unless necessary. Development of rust-analyzer happens at https://github.com/rust-lang/rust-analyzer/
There was a problem hiding this comment.
rebased
For future reference do all subtrees have a josh-sync.toml?
There was a problem hiding this comment.
Most do. The exceptions I believe are compiler/rustc_codegen_cranelift, compiler/rustc_codegen_gcc and src/tools/rustfmt. Those I think are the only ones that still use git-subtree rather than josh for syncing.
There was a problem hiding this comment.
Right, unfortunately there is no reliable method get a list of current subtrees from Git. Perhaps these could be tracked explicitly somewhere?
There was a problem hiding this comment.
No need to, just see if triagebot complains. You can skim https://github.com/rust-lang/rust/blob/main/triagebot.toml if you're wondering.
There was a problem hiding this comment.
I don't think this is necessary, so please remove this change.
There was a problem hiding this comment.
OK I've rebased to remove changes under src/tools/rust-analyzer
I've added the change to src/tools/compiletest back since that doesn't appear to be a subtree.
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Replace `truncate(0)` with `clear()`
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (637b2a9): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 0.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 481.003s -> 480.752s (-0.05%) |
There was a problem hiding this comment.
I don't think this is necessary, so please remove this change.
|
Reminder, once the PR becomes ready for a review, use |
|
@rustbot ready |
|
Thanks! |
Rollup of 11 pull requests Successful merges: - #152880 (Tweak incorrect assoc item note) - #153526 (Fix LegacyKeyValueFormat report from docker build: i686) - #153613 (interpreter error reporting: remove arguments that are always the same) - #154029 (Replace `truncate(0)` with `clear()`) - #154125 (Inline and remove `DepGraphData::try_mark_parent_green`.) - #154185 (Prevent no_threads RwLock's write() impl from setting mode to -1 when it is locked for reading) - #154394 (Normalize rustc path prefix when testing `-Z track-diagnostics`) - #154450 (Use the normal arg-parsing machinery for `-Zassert-incr-state`) - #154475 (Emit a pre-expansion feature gate warning for `box`'ed struct field patterns) - #154500 (EnumSizeOpt: use Allocation::write_scalar instead of manual endianess logic) - #154502 (interpret: ensure that untupled arguments are actually tuples)
Rollup merge of #154029 - xtqqczze:clear, r=joboet Replace `truncate(0)` with `clear()`
No description provided.