Rollup of 8 pull requests #127819
Rollup of 8 pull requests #127819
Commits on Jul 16, 2024
-
Use an iterator to find
expand_untilThis makes it easier to see that the split point is always the index after the found item, or the whole list if no stopping point was found.
-
delete #![allow(unsafe_op_in_unsafe_fn)]
this is redundant, so we can just delete it.
-
-
-
-
-
-
-
-
-
-
-
-
-
Fix a bunch of sites that were walking instead of visiting, making it…
… impossible for visitor impls to look at these values
-
Rollup merge of rust-lang#127669 - chenyukang:yukang-fix-deref-127590…
…, r=nnethercote Fix the issue of invalid suggestion for a reference of iterator Fixes rust-lang#127590
-
Rollup merge of rust-lang#127707 - Zalathar:expand-until, r=Nadrieril
match lowering: Use an iterator to find `expand_until` A small cleanup that I noticed while looking at rust-lang#127164. This makes it easier to see that the split point is always the index after the found item, or the whole list if no stopping point was found. r? `@Nadrieril`
-
Rollup merge of rust-lang#127730 - compiler-errors:ed-2024-unsafe, r=…
…petrochenkov Fix and enforce `unsafe_op_in_unsafe_fn` in compiler In preparation for edition 2024, this PR previews the fallout of enabling the `unsafe_op_in_unsafe_fn` lint in the compiler, since it's defaulting to warn in the new edition (rust-lang#112038). The major annoyance comes primarily from the `rustc_codegen_llvm` module, where there's a ton of unsafe calls. I tended to wrap individual calls to unsafe fns in `unsafe {}`, but there a handful of places I chose to just wrap several calls in an `unsafe {}` block just because it would've been excessive to wrap each call individually. This doesn't enable the lint for the standard library, since I'm not totally certain what T-libs prefers w/ this lint.
-
Rollup merge of rust-lang#127789 - Sword-Destiny:master, r=petrochenkov
delete #![allow(unsafe_op_in_unsafe_fn)] in teeos deny unsafe_op_in_unsafe_fn for teeos
-
Rollup merge of rust-lang#127805 - Mrmaxmeier:run-make-bump-gimli, r=…
…jieyouxu run-make-support: update gimli to 0.31.0 This version bump is required for the tests in rust-lang#126985 as suggested [here](rust-lang#126985 (comment)). r? tgross35 (^ that didn't work. cc `@tgross35)` try-job: x86_64-msvc try-job: x86_64-mingw try-job: aarch64-apple try-job: test-various try-job: armhf-gnu try-job: dist-x86_64-linux
-
Rollup merge of rust-lang#127808 - oli-obk:tainting_visitors2, r=lcnr…
…,nnethercote Make ErrorGuaranteed discoverable outside types, consts, and lifetimes types like `PatKind` could contain `ErrorGuaranteed`, but not return them via `tainted_by_errors` or `error_reported` (see rust-lang#127687 (comment)). Now this happens, but it's a bit fragile as you can see with the `TypeSuperVisitable for Ty` impl. We will catch any problems around Ty, Region or Const at runtime with an assert, and everything using derives will not have such issues, as it will just invoke the `TypeVisitable for ErrorGuaranteed` impl
-
Rollup merge of rust-lang#127817 - oli-obk:mut_visitor_fix, r=petroch…
…enkov Fix a bunch of sites that were walking instead of visiting, making it impossible for visitor impls to look at these values This doesn't affects anything right now, but a `MutVisitor` impl could be surprised by this. The reason this doesn't affect anything is that no one overrrides `visit_lifetime` or `visit_param_bounds` currently.
-
Rollup merge of rust-lang#127818 - oli-obk:ast_validation_simplificat…
…ions, r=petrochenkov Various ast validation simplifications Changes pulled out of rust-lang#127524 These are needed to make ast validation a mutable visitor, as we can't keep immutable references to the AST around in that case. But I think they are simplifying things in general and can stand on their own
