-
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
Rollup of 8 pull requests #122866
Rollup of 8 pull requests #122866
Commits on Mar 6, 2024
-
Add postfix-match experimental feature
Co-authored-by: Josh Stone <jistone@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 68a58f2 - Browse repository at this point
Copy the full SHA 68a58f2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 78b3bf9 - Browse repository at this point
Copy the full SHA 78b3bf9View commit details -
Configuration menu - View commit details
-
Copy full SHA for d4ba888 - Browse repository at this point
Copy the full SHA d4ba888View commit details -
Configuration menu - View commit details
-
Copy full SHA for 567c98b - Browse repository at this point
Copy the full SHA 567c98bView commit details
Commits on Mar 15, 2024
-
interpret/allocation: fix aliasing issue in interpreter and refactor …
…getters a bit - rename mutating functions to be more scary - add a new raw bytes getter
Configuration menu - View commit details
-
Copy full SHA for 7be47b2 - Browse repository at this point
Copy the full SHA 7be47b2View commit details
Commits on Mar 19, 2024
-
Gracefully handle AnonConst in diagnostic_hir_wf_check()
when it is the default value of a generic param
Configuration menu - View commit details
-
Copy full SHA for 3c70d60 - Browse repository at this point
Copy the full SHA 3c70d60View commit details
Commits on Mar 20, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 4250216 - Browse repository at this point
Copy the full SHA 4250216View commit details
Commits on Mar 21, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 453676f - Browse repository at this point
Copy the full SHA 453676fView commit details -
Use != Positive rather than == Negative
Feels more complete, and for ImplPolarity has the side-effect of making sure we also handle reservation impls correctly
Configuration menu - View commit details
-
Copy full SHA for 76ad048 - Browse repository at this point
Copy the full SHA 76ad048View commit details -
Configuration menu - View commit details
-
Copy full SHA for 08d8cd5 - Browse repository at this point
Copy the full SHA 08d8cd5View commit details -
Configuration menu - View commit details
-
Copy full SHA for dae3c43 - Browse repository at this point
Copy the full SHA dae3c43View commit details -
Configuration menu - View commit details
-
Copy full SHA for 60891ca - Browse repository at this point
Copy the full SHA 60891caView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5425338 - Browse repository at this point
Copy the full SHA 5425338View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1b95760 - Browse repository at this point
Copy the full SHA 1b95760View commit details
Commits on Mar 22, 2024
-
Arrays, surprisingly, are not sized to u64 on all platforms.
Configuration menu - View commit details
-
Copy full SHA for 861e470 - Browse repository at this point
Copy the full SHA 861e470View commit details -
coverage: Clean up marker statements that aren't needed later
Some of the marker statements used by coverage are added during MIR building for use by the InstrumentCoverage pass (during analysis), and are not needed afterwards.
Configuration menu - View commit details
-
Copy full SHA for 91aae58 - Browse repository at this point
Copy the full SHA 91aae58View commit details -
Rollup merge of rust-lang#121619 - RossSmyth:pfix_match, r=petrochenkov
Experimental feature postfix match This has a basic experimental implementation for the RFC postfix match (rust-lang/rfcs#3295, rust-lang#121618). [Liaison is](https://rust-lang.zulipchat.com/#narrow/stream/213817-t-lang/topic/Postfix.20Match.20Liaison/near/423301844) `@scottmcm` with the lang team's [experimental feature gate process](https://github.com/rust-lang/lang-team/blob/master/src/how_to/experiment.md). This feature has had an RFC for a while, and there has been discussion on it for a while. It would probably be valuable to see it out in the field rather than continue discussing it. This feature also allows to see how popular postfix expressions like this are for the postfix macros RFC, as those will take more time to implement. It is entirely implemented in the parser, so it should be relatively easy to remove if needed. This PR is split in to 5 commits to ease review. 1. The implementation of the feature & gating. 2. Add a MatchKind field, fix uses, fix pretty. 3. Basic rustfmt impl, as rustfmt crashes upon seeing this syntax without a fix. 4. Add new MatchSource to HIR for Clippy & other HIR consumers
Configuration menu - View commit details
-
Copy full SHA for 05f612d - Browse repository at this point
Copy the full SHA 05f612dView commit details -
Rollup merge of rust-lang#122370 - gurry:122199-ice-unexpected-node, …
…r=davidtwco Gracefully handle `AnonConst` in `diagnostic_hir_wf_check()` Instead of running the WF check on the `AnonConst` itself we run it on the `ty` of the generic param of which the `AnonConst` is the default value. Fixes rust-lang#122199
Configuration menu - View commit details
-
Copy full SHA for 665c7a2 - Browse repository at this point
Copy the full SHA 665c7a2View commit details -
Rollup merge of rust-lang#122537 - RalfJung:interpret-allocation, r=o…
…li-obk interpret/allocation: fix aliasing issue in interpreter and refactor getters a bit That new raw getter will be needed to let Miri pass pointers to natively executed FFI code ("extern-so" mode). While doing that I realized our get_bytes_mut are named less scary than get_bytes_unchecked so I rectified that. Also I realized `mem_copy_repeatedly` would break if we called it for multiple overlapping copies so I made sure this does not happen. And I realized that we are actually [violating Stacked Borrows in the interpreter](https://rust-lang.zulipchat.com/#narrow/stream/136281-t-opsem/topic/I.20think.20Miri.20violates.20Stacked.20Borrows.20.F0.9F.99.88).^^ That was introduced in rust-lang#87777. r? `@oli-obk`
Configuration menu - View commit details
-
Copy full SHA for d141d9a - Browse repository at this point
Copy the full SHA d141d9aView commit details -
Rollup merge of rust-lang#122542 - Zalathar:cleanup, r=oli-obk
coverage: Clean up marker statements that aren't needed later Some of the marker statements used by coverage are added during MIR building for use by the InstrumentCoverage pass (during analysis), and are not needed afterwards. `@rustbot` label +A-code-coverage
Configuration menu - View commit details
-
Copy full SHA for 2a54c13 - Browse repository at this point
Copy the full SHA 2a54c13View commit details -
Rollup merge of rust-lang#122800 - zachs18:nonnull-slice-is_empty, r=…
…Amanieu Add `NonNull::<[T]>::is_empty`. As per rust-lang#71146 (comment) I figured this should be fine to be insta-stable (with an FCP), but I can edit if that is not desired. r? `@Amanieu`
Configuration menu - View commit details
-
Copy full SHA for 75fa268 - Browse repository at this point
Copy the full SHA 75fa268View commit details -
Rollup merge of rust-lang#122839 - compiler-errors:predicate-polarity…
…, r=lcnr Split out `PredicatePolarity` from `ImplPolarity` Because having to deal with a third `Reservation` level in all the trait solver code is kind of weird. r? ``@lcnr`` or ``@oli-obk``
Configuration menu - View commit details
-
Copy full SHA for 0947f2e - Browse repository at this point
Copy the full SHA 0947f2eView commit details -
Rollup merge of rust-lang#122847 - workingjubilee:suggest-rust-min-st…
…ack-workaround-on-overflow, r=TaKO8Ki Suggest `RUST_MIN_STACK` workaround on overflow For some Rust crates, like p384, we can't do a whole lot about it even if the stack overflow is reported like in rust-lang#122357 because the problem may be inside LLVM or another codegen backend. We can, however, suggest people set a new `RUST_MIN_STACK` value while handling the SIGSEGV, as that stack-setting will carry forward into the dylib. As a bonus, this also leads to cleaning up the stack-setting code a bit.
Configuration menu - View commit details
-
Copy full SHA for 61561fe - Browse repository at this point
Copy the full SHA 61561feView commit details -
Rollup merge of rust-lang#122855 - workingjubilee:mangle-64-bit-chauv…
…inism, r=compiler-errors Fix Itanium mangling usizes Arrays, surprisingly, are not sized to u64 on all platforms. Fixes rust-lang#122851. r? `@compiler-errors` cc `@maurer`
Configuration menu - View commit details
-
Copy full SHA for e5fcc6a - Browse repository at this point
Copy the full SHA e5fcc6aView commit details