-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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 6 pull requests #89671
Rollup of 6 pull requests #89671
Commits on Jul 28, 2021
-
stack overflow handler specific openbsd fix.
On this platform, when doing stack allocation, MAP_STACK is needed otherwise the mapping fails.
Configuration menu - View commit details
-
Copy full SHA for 853ffc7 - Browse repository at this point
Copy the full SHA 853ffc7View commit details
Commits on Oct 5, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 10f7769 - Browse repository at this point
Copy the full SHA 10f7769View commit details -
Configuration menu - View commit details
-
Copy full SHA for 64c794c - Browse repository at this point
Copy the full SHA 64c794cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 7df32f4 - Browse repository at this point
Copy the full SHA 7df32f4View commit details -
Configuration menu - View commit details
-
Copy full SHA for b7191b3 - Browse repository at this point
Copy the full SHA b7191b3View commit details -
Re-use logic for adding a suggestion when a lifetime bound is missing…
… on an impl trait
Configuration menu - View commit details
-
Copy full SHA for d3871f5 - Browse repository at this point
Copy the full SHA d3871f5View commit details
Commits on Oct 6, 2021
-
Fix stabilization version for
bindings_after_at
According to the release notes and its PR milestone, it was stabilized in 1.56.0.
Configuration menu - View commit details
-
Copy full SHA for 6189d0a - Browse repository at this point
Copy the full SHA 6189d0aView commit details
Commits on Oct 8, 2021
-
Configuration menu - View commit details
-
Copy full SHA for cbf9153 - Browse repository at this point
Copy the full SHA cbf9153View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3215403 - Browse repository at this point
Copy the full SHA 3215403View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4593d78 - Browse repository at this point
Copy the full SHA 4593d78View commit details -
Configuration menu - View commit details
-
Copy full SHA for 31b2eb1 - Browse repository at this point
Copy the full SHA 31b2eb1View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0a03ec4 - Browse repository at this point
Copy the full SHA 0a03ec4View commit details -
Rollup merge of rust-lang#86506 - b-naber:gen_trait_impl_inconsistent…
…, r=jackh726 Don't normalize xform_ret_ty during method candidate assembly Fixes rust-lang#85671 Normalizing the return type of a method candidate together with the expected receiver type of the method can lead to valid method candidates being rejected during probing. Specifically in the example of the fixed issue we have a `self_ty` of the form `&A<&[Coef]>` whereas the `impl_ty` of the method would be `&A<_>`, if we normalize the projection in the return type we unify the inference variable with `Cont`, which will lead us to reject the candidate in the sup type check in `consider_probe`. Since we don't actually need the normalized return type during candidate assembly, we postpone the normalization until we consider candidates in `consider_probe`.
Configuration menu - View commit details
-
Copy full SHA for 9d1dc71 - Browse repository at this point
Copy the full SHA 9d1dc71View commit details -
Rollup merge of rust-lang#87528 - :stack_overflow_obsd, r=joshtriplett
stack overflow handler specific openbsd change.
Configuration menu - View commit details
-
Copy full SHA for bc70f7d - Browse repository at this point
Copy the full SHA bc70f7dView commit details -
Rollup merge of rust-lang#89555 - oli-obk:nll_member_constraint_diag,…
… r=estebank Remove textual span from diagnostic string This is an unnecessary repetition, as the diagnostic prints the span anyway in the source path right below the message. I further removed the identification of the node, as that does not give any new information in any of the cases that are changed in tests. EDIT: also inserted a suggestion that other diagnostics were already emitting
Configuration menu - View commit details
-
Copy full SHA for 57b9602 - Browse repository at this point
Copy the full SHA 57b9602View commit details -
Rollup merge of rust-lang#89605 - camelid:fix-version, r=nagisa
Fix stabilization version for `bindings_after_at` According to the release notes and its PR milestone, it was stabilized in 1.56.0.
Configuration menu - View commit details
-
Copy full SHA for c52602f - Browse repository at this point
Copy the full SHA c52602fView commit details -
Rollup merge of rust-lang#89666 - rusticstuff:disable_new_llvm_pass_m…
…anager_on_s390x_take_two, r=nagisa Default to disabling the new pass manager for the s390x arch targets. This hack disables the new LLVM pass manager by default for s390x arch targets until the performance issues are fixed (see rust-lang#89609). The command line option `-Z new-llvm-pass-manager=(yes|no)` continues to take precedence over this default.
Configuration menu - View commit details
-
Copy full SHA for d7bb8a7 - Browse repository at this point
Copy the full SHA d7bb8a7View commit details -
Rollup merge of rust-lang#89668 - Urgau:core-cfg-hide, r=GuillaumeGomez
Cfg hide more conditions for core and alloc Fixes rust-lang#89663 Before: ![image](https://user-images.githubusercontent.com/3616612/136572816-a7844ac7-dc2f-4d79-87b4-7f9766421a83.png) After: ![image](https://user-images.githubusercontent.com/3616612/136572745-7d890726-8efd-4d74-83ac-ed06f4687741.png) *Same for alloc* r? `@GuillaumeGomez`
Configuration menu - View commit details
-
Copy full SHA for 66f5f12 - Browse repository at this point
Copy the full SHA 66f5f12View commit details