| Age | Commit message (Collapse) | Author | Lines |
|
Added a single character to fix a typo in a doc comment.
|
|
|
|
|
|
The new bots we have may conflict with one another on base ports, causing tests
to fail. For example the linux-musl-64-opt and linux-64-opt bots are using the
same base port right now, causing some spurious failures every now and then.
|
|
PR for #28157. At the moment, `rustc` emits a warning when a bare semicolon is encountered (could also be a fail, but I think this is a backwards incompatible change).
Also I am not sure where the best place for a test for that warning would be. Seems run-pass tests do not check warnings.
|
|
|
|
The new bots we have may conflict with one another on base ports, causing tests
to fail. For example the linux-musl-64-opt and linux-64-opt bots are using the
same base port right now, causing some spurious failures every now and then.
|
|
|
|
{BTree,Hash}{Map,Set} will not update their key if it already exists, which
can matter with more complex keys. This behavior is now documented.
Fixes #26888
|
|
{BTree,Hash}{Map,Set} will not update their key if it already exists, which
can matter with more complex keys. This behavior is now documented.
Fixes #26888
|
|
Fixes #29219
|
|
|
|
This was already implemented for SocketAddr, so the other types are lacking it
is just an oversight!
Closes #29183
|
|
- Successful merges: #29158, #29162, #29175, #29176
- Failed merges:
|
|
This test was mysteriously messed with as part of #28500
r? @alexcrichton
|
|
Just some minor cleanup.
|
|
Fixes #29150
r? @alexcrichton
|
|
|
|
r? @steveklabnik
|
|
Just a few minor spelling/grammar fixes.
|
|
|
|
`OsString` has these sorts of conversions, while `CString` has been missing them. I'm iffy on `into_string` simply because the return type would be better off as `FromUtf8Error<CString>`, which of course isn't generic :cry:
Also should a different/new feature gate be used?
|
|
|
|
Fixes #29150
Signed-off-by: Peter Atashian <retep998@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
`rbml::writer::Encoder::unsafe_clone` had no users across the entire
repo.
|
|
|
|
This change has two consequences:
1. It makes `Arc<T>` and `Rc<T>` covariant in `T`.
2. It causes the compiler to reject code that was unsound with respect
to dropck. See compile-fail/issue-29106.rs for an example of code that
no longer compiles. Because of this, this is a [breaking-change].
Fixes #29037.
Fixes #29106.
|
|
The implementation for `into_inner` was a bit more complex than I had hoped for---is there any simpler, less unsafe way of getting around the fact that one can't move out of a `Drop` struct?
See #28968 and rust-lang/rfcs#1269 .
|
|
|
|
|
|
This commit adds `#[derive(Clone)]` to `std::fs::Metadata`, making that struct cloneable. Although the exact contents of that struct differ between OSes, they all have it contain only value types, meaning that the data can be re-used without repercussions.
It also adds `#[derive(Clone)]` to every type used by that struct across all OSes, including the various Unix `stat` structs and Windows's `WIN32_FILE_ATTRIBUTE_DATA`.
This stems from my comment here: https://github.com/rust-lang/rfcs/issues/939#issuecomment-140524439
|
|
r? @alexcrichton
|
|
None
|
|
r? @steveklabnik
|
|
|
|
Fixes #28995.
|
|
|
|
|
|
The link is broken here: <https://doc.rust-lang.org/std/io/#types>.
Looks like crate documentation generator uses only first paragraph of the module documentation and
so doesn't resolve the link defined below.
|
|
|
|
This commit adds #[derive(Clone)] to std::fs::Metadata, making that struct
cloneable. Although the exact contents of that struct differ between OSes,
they all have it contain only value types, meaning that the data can be re-used without repercussions.
It also adds #[derive(Clone)] to every type used by that struct across all
OSes, including the various Unix `stat` structs and Windows's
`WIN32_FILE_ATTRIBUTE_DATA`.
|
|
|
|
This concern was raised by #28940.
|
|
implement RFC 1238: nonparametric dropck.
cc #28498
cc @nikomatsakis
|
|
|