-
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 9 pull requests #88556
Rollup of 9 pull requests #88556
Commits on Aug 15, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 21f07b5 - Browse repository at this point
Copy the full SHA 21f07b5View commit details
Commits on Aug 18, 2021
-
Configuration menu - View commit details
-
Copy full SHA for f33f266 - Browse repository at this point
Copy the full SHA f33f266View commit details
Commits on Aug 26, 2021
-
add support for clobbering xer, cr, and cr[0-7] for asm! on OpenPower…
…/PowerPC Fixes rust-lang#88315
Configuration menu - View commit details
-
Copy full SHA for 5802f60 - Browse repository at this point
Copy the full SHA 5802f60View commit details
Commits on Aug 30, 2021
-
emit specific warning to clarify that foreign items can't have no_mangle
remove extra commented code Deduplicate some diagnostics code add code symbols, machine applicable suggestion clarify error message
Configuration menu - View commit details
-
Copy full SHA for fc125a5 - Browse repository at this point
Copy the full SHA fc125a5View commit details
Commits on Aug 31, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 026322c - Browse repository at this point
Copy the full SHA 026322cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 435cdd0 - Browse repository at this point
Copy the full SHA 435cdd0View commit details -
Change wording to less jaron-y "non-auto trait"
Co-authored-by: Vadim Petrochenkov <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 6e70678 - Browse repository at this point
Copy the full SHA 6e70678View commit details -
Remove bolding on associated constants
Associated types don't get bolded, so it looks off to have one kind bolded and one not.
Configuration menu - View commit details
-
Copy full SHA for 87e39ac - Browse repository at this point
Copy the full SHA 87e39acView commit details -
Use the return value of readdir_r() instead of errno
POSIX says: > If successful, the readdir_r() function shall return zero; otherwise, > an error number shall be returned to indicate the error. But we were previously using errno instead of the return value. This led to issue rust-lang#86649.
Configuration menu - View commit details
-
Copy full SHA for 0e0c8ae - Browse repository at this point
Copy the full SHA 0e0c8aeView commit details -
Configuration menu - View commit details
-
Copy full SHA for 753dac1 - Browse repository at this point
Copy the full SHA 753dac1View commit details -
Configuration menu - View commit details
-
Copy full SHA for 06dd4c0 - Browse repository at this point
Copy the full SHA 06dd4c0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 227e004 - Browse repository at this point
Copy the full SHA 227e004View commit details
Commits on Sep 1, 2021
-
Rollup merge of rust-lang#86376 - asquared31415:extern-no-mangle-8420…
…4, r=Mark-Simulacrum Emit specific warning to clarify that `#[no_mangle]` should not be applied on foreign statics or functions Foreign statics and foreign functions should not have `#[no_mangle]` applied, as it does nothing to the name and has some extra hidden behavior that is normally unwanted. There was an existing warning for this, but it says the attribute is only allowed on "statics or functions", which to the user can be confusing. This PR adds a specific version of the unused `#[no_mangle]` warning that explains that the target is a *foreign* static or function and that they do not need the attribute. Fixes rust-lang#78989
Configuration menu - View commit details
-
Copy full SHA for dcefd68 - Browse repository at this point
Copy the full SHA dcefd68View commit details -
Rollup merge of rust-lang#88040 - nbdd0121:btreemap, r=m-ou-se
BTree: remove Ord bound from new `K: Ord` bound is unnecessary on `BTree{Map,Set}::new` and their `Default` impl. No elements exist so there are nothing to compare anyway, so I don't think "future proof" would be a blocker here. This is analogous to `HashMap::new` not having a `K: Eq + Hash` bound. rust-lang#79245 originally does this and for some reason drops the change to `new` and `Default`. I can see why changes to other methods like `entry` or `symmetric_difference` need to be careful but I couldn't find out any reason not to do it on `new`. Removing the bound also makes the stabilisation of `const fn new` not depending on const trait bounds. cc `@steffahn` who suggests me to make this PR. r? `@dtolnay`
Configuration menu - View commit details
-
Copy full SHA for 5878780 - Browse repository at this point
Copy the full SHA 5878780View commit details -
Rollup merge of rust-lang#88053 - bjorn3:fix_flock_fallback_impl, r=c…
…jgillot Fix the flock fallback implementation
Configuration menu - View commit details
-
Copy full SHA for 8fd53e3 - Browse repository at this point
Copy the full SHA 8fd53e3View commit details -
Rollup merge of rust-lang#88350 - programmerjake:add-ppc-cr-xer-clobb…
…ers, r=Amanieu add support for clobbering xer, cr, and cr[0-7] for asm! on OpenPower/PowerPC Fixes rust-lang#88315
Configuration menu - View commit details
-
Copy full SHA for 494c563 - Browse repository at this point
Copy the full SHA 494c563View commit details -
Rollup merge of rust-lang#88410 - camelid:fix-assoc-bold, r=Guillaume…
…Gomez Remove bolding on associated constants Associated types don't get bolded, so it looks off to have one kind bolded and one not.
Configuration menu - View commit details
-
Copy full SHA for 75b2ae5 - Browse repository at this point
Copy the full SHA 75b2ae5View commit details -
Rollup merge of rust-lang#88525 - notriddle:notriddle/coherence-dyn-a…
…uto-trait, r=petrochenkov fix(rustc_typeck): produce better errors for dyn auto trait Fixes rust-lang#85026
Configuration menu - View commit details
-
Copy full SHA for bbc94ed - Browse repository at this point
Copy the full SHA bbc94edView commit details -
Rollup merge of rust-lang#88542 - tavianator:readdir_r-errno, r=jyn514
Use the return value of readdir_r() instead of errno POSIX says: > If successful, the readdir_r() function shall return zero; otherwise, > an error number shall be returned to indicate the error. But we were previously using errno instead of the return value. This led to issue rust-lang#86649.
Configuration menu - View commit details
-
Copy full SHA for 59588a9 - Browse repository at this point
Copy the full SHA 59588a9View commit details -
Rollup merge of rust-lang#88548 - inquisitivecrystal:intersperse, r=m…
…-ou-se Stabilize `Iterator::intersperse()` This PR stabilizes the methods `Iterator::intersperse()` and `Iterator::intersperse_with()`. The FCP has [already completed](rust-lang#79524 (comment)). Closes rust-lang#79524.
Configuration menu - View commit details
-
Copy full SHA for f436b6d - Browse repository at this point
Copy the full SHA f436b6dView commit details -
Rollup merge of rust-lang#88551 - inquisitivecrystal:unsafe_cell_raw_…
…get, r=m-ou-se Stabilize `UnsafeCell::raw_get()` This PR stabilizes the associated function `UnsafeCell::raw_get()`. The FCP has [already completed](rust-lang#66358 (comment)). While there was some discussion about the naming after the close of the FCP, it looks like people have agreed on this name. Still, it would probably be best if a `libs-api` member had a look at this and stated whether more discussion is needed. While I was at it, I added some tests for `UnsafeCell`, because there were barely any. Closes rust-lang#66358.
Configuration menu - View commit details
-
Copy full SHA for d313529 - Browse repository at this point
Copy the full SHA d313529View commit details