-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
[beta] backports #85588
[beta] backports #85588
Commits on May 22, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 5a2dbd0 - Browse repository at this point
Copy the full SHA 5a2dbd0View commit details -
remove InPlaceIterable marker from Peekable due to unsoundness
The unsoundness is not in Peekable per se, it rather is due to the interaction between Peekable being able to hold an extra item and vec::IntoIter's clone implementation shortening the allocation. An alternative solution would be to change IntoIter's clone implementation to keep enough spare capacity available.
Configuration menu - View commit details
-
Copy full SHA for 586b51a - Browse repository at this point
Copy the full SHA 586b51aView commit details -
Configuration menu - View commit details
-
Copy full SHA for c47274b - Browse repository at this point
Copy the full SHA c47274bView commit details -
This also checks the contents and not only the capacity in case IntoIter's clone implementation is changed to add capacity at the end. Extra capacity at the beginning would be needed to make InPlaceIterable work. Co-authored-by: Giacomo Stevanato <giaco.stevanato@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for ff346b9 - Browse repository at this point
Copy the full SHA ff346b9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 855a573 - Browse repository at this point
Copy the full SHA 855a573View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5d1125d - Browse repository at this point
Copy the full SHA 5d1125dView commit details -
Do not ICE on invalid const param
When encountering a path that can't have generics, do not call `generics_of`. This would happen when writing something like `path::this_is_a_mod<const_val>`. Fix rust-lang#84831.
Configuration menu - View commit details
-
Copy full SHA for e68af12 - Browse repository at this point
Copy the full SHA e68af12View commit details -
Disallows
#![feature(no_coverage)]
on stable and betausing allow_internal_unstable (as recommended) Fixes: rust-lang#84836 ```shell $ ./build/x86_64-unknown-linux-gnu/stage1/bin/rustc src/test/run-make-fulldeps/coverage/no_cov_crate.rs error[E0554]: `#![feature]` may not be used on the dev release channel --> src/test/run-make-fulldeps/coverage/no_cov_crate.rs:2:1 | 2 | #![feature(no_coverage)] | ^^^^^^^^^^^^^^^^^^^^^^^^ error: aborting due to previous error For more information about this error, try `rustc --explain E0554`. ```
Configuration menu - View commit details
-
Copy full SHA for d1e2499 - Browse repository at this point
Copy the full SHA d1e2499View commit details -
Configuration menu - View commit details
-
Copy full SHA for c297d1e - Browse repository at this point
Copy the full SHA c297d1eView commit details -
Use atomics in join_orders_after_tls_destructors test
std::sync::mpsc uses thread locals and depending on the order TLS dtors are run `rx.recv()` can panic when used in a TLS dtor.
Configuration menu - View commit details
-
Copy full SHA for 5d1fdf4 - Browse repository at this point
Copy the full SHA 5d1fdf4View commit details -
join_orders_after_tls_destructors: ensure thread 2 is launched before…
… thread 1 enters TLS destructors
Configuration menu - View commit details
-
Copy full SHA for 0e49ff0 - Browse repository at this point
Copy the full SHA 0e49ff0View commit details