| Age | Commit message (Collapse) | Author | Lines |
|
|
|
|
|
|
|
This helps us have enough disk space for our builders to be able to complete
successfully. For now, the choices are ad-hoc and 'definitely not needed'. This
should never fail the build, as everything our build needs should be inside
Docker.
|
|
|
|
|
|
This extends the existing logic which skips validating every integer or
floating point number type to also skip validating empty structs because
they are also trivially valid.
Fixes #67539
|
|
|
|
|
|
This fixes a a segfault in safe code, a stable regression. Reported in
\#69225.
This reverts commit a983e0590a43ed8b0f60417828efd4e79b51f494.
Also adds a test for the expected behaviour.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I believe rustdoc should not be conflating private items (visibility
lower than `pub`) and hidden items (attribute `doc(hidden)`). This
matters now that Cargo is passing --document-private-items by default
for bin crates. In bin crates that rely on macros, intentionally hidden
implementation details of the macros can overwhelm the actual useful
internal API that one would want to document.
This PR restores the strip-hidden pass when documenting private items,
and introduces a separate unstable --document-hidden-items option to
skip the strip-hidden pass. The two options are orthogonal to one
another.
|
|
|
|
Because it caused major performance regressions in some cases.
That PR had five commits, two of which affected performance, and three
of which were refactorings. This change undoes the performance-affecting
changes, while keeping the refactorings in place.
Fixes #67454.
|
|
|
|
(cherry picked from commit 40571995984a0f2c466f77955e7d147887c2179b)
|
|
(cherry picked from commit f6e9fd037a7b55f8f4fe78694b77d9788b18dfeb)
|
|
(cherry picked from commit b93ef68245807bac97cd17ea9eaa13169380d815)
|
|
(cherry picked from commit d558f6a570a782cd1c2e54de790f4f968b0de5f1)
|
|
(cherry picked from commit 3250057da983fa4d5bfd0799adaa41cb038f0e25)
|
|
Use `shrink_to_hi` instead of `next_point`
Fix #68000.
(cherry picked from commit fcd850fc5db2501d14b2e0cbfac8aa890d700e55)
|
|
(cherry picked from commit 915db7ae6430baef99f186ba40f08e105b7694fe)
|
|
|
|
|
|
representation
|
|
|
|
|
|
|
|
|
|
PR https://github.com/rust-lang/rust/pull/66512 added the ability to set argv[0] on
Command. As a side effect, it changed the Debug output to print both the program and
argv[0], which in practice results in stuttery output ("echo echo foo").
This PR reverts the behaviour to the the old one, so that the command is only printed
once - unless arg0 has been set. In that case it emits "[command] arg0 arg1 ...".
|
|
|
|
Minor: update Unsize docs for dyn syntax
|
|
Fix JS error when loading page with search
For example when you load this page: https://doc.rust-lang.org/nightly/std/num/struct.NonZeroI8.html?search=foo, you get a nice JS error:
```
TypeError: ev is undefined
```
r? @kinnison
|
|
make transparent enums more ordinary
By recognizing that structs & unions have one variant, we can make the treatment of transparent enums less ad-hoc.
cc https://github.com/rust-lang/rust/issues/60405
r? @davidtwco
|
|
use Self alias in place of macros
|
|
Improve typeck & lowering docs for slice patterns
cc #62254
r? @matthewjasper
|
|
Delete flaky test net::tcp::tests::fast_rebind
This test is unreliable for at least 3 users on two platforms: see #57509 and #51006. It was added 5 years ago in #22015. Do we know whether this is testing something important that would indicate a bug in our implementation, or if it's fine to remove?
r? @sfackler @alexcrichton because this somewhat resembles #59018
Closes #57509. Closes #51006.
|
|
Improve code generated for `starts_with(<literal char>)`
This PR includes two minor improvements to the code generated when checking for string prefix/suffix.
The first commit simplifies the str/str operation, by taking advantage of the raw UTF-8 representation.
The second commit replaces the current str/char matching logic with a char->str encoding and then the previous method.
The resulting code should be equivalent in the generic case (one char is being encoded versus one char being decoded), but it becomes easy to optimize in the case of a literal char, which in most cases a developer might expect to be at least as simple as that of a literal string.
This PR should fix #41993
|
|
|
|
|
|
|
|
cleanup with push_fake_read
...and make things a bit more readable.
r? @matthewjasper
|
|
Fix repetition in matches/mod.rs
r? @matthewjasper
|