| Age | Commit message (Collapse) | Author | Lines |
|
[stable] Prepare Rust 1.69.0
Last minute backports:
* #109643
* #110135
* #109938
* #109937
* #109266
This PR also bumps the channel to stable, and backports the release notes from master.
r? `@ghost`
cc `@rust-lang/release`
|
|
|
|
|
|
|
|
|
|
and make it fallible
|
|
Reverts PR #108031
Fixes (doesnt close until beta backported) #109746
This reverts commit e3f9db5fc319c6d8eee5d47d216ea6a426070c41.
This reverts commit 98b82aedba3f3f581e89df54352914b27f42c6f7.
This reverts commit 380fa264132ad481e73cbbf0f3a0feefd99a1d78.
|
|
This is another attempt to work around
https://github.com/rust-lang/rust/issues/108227.
By limiting to one link job, we should be able to avoid file name
clashes in mkstemp().
|
|
[beta] Clippy: backport optimization and ICE fixes
The first commit optimizes a lint, that runs noticeably slow and is a perf issue. See https://github.com/rust-lang/rust-clippy/pull/10533
The second commit fixes an ICE that occurred when running Clippy on `gitoxide` besides others. Since this is a rather popular crate, we want to fix this rather sooner than later. See https://github.com/rust-lang/rust-clippy/pull/10403
---
Both commits are already on `master` and deployed on `nightly`.
|
|
|
|
The lint is very slow as it doesn't cache the deeply nested check for
the attribute. If we cache it, we can reduce the time spent on checking
`rustc_borrowck` from 28s to 9s, which is a nice improvement. In the
profile, the time inside `has_sig_drop_attr` goes from 66% to 0.2%,
which is a lot more reasonable.
See the PR for nice graphs.
|
|
[beta-1.69] cargo backport
1 commits in 713164a40962a0a76c7f3ad8aafb6f03410e21d2..6e9a83356b70586d4b77613a6b33f9ea067b9cdf
2023-03-26 20:05:25 +0000 to 2023-04-12 10:18:25 +0000
- [beta 1.69] Change -C to be unstable (rust-lang/cargo#11961)
r? `@ghost`
|
|
|
|
[beta] backport
This PR backports:
- #109332: Move us to the new large runners pool
- #109156: Fix linker detection for clang with prefix
- #109111: Create dirs for build_triple
- #109094: Revert "enable ThinLTO for rustc on x86_64-pc-windows-msvc dist builds"
Also bumps us to the latest released stable, 1.68.2.
r? `@Mark-Simulacrum`
|
|
Revert 102245
reverts #102245, but only on beta, as that caused #109543 which has since been fixed on nightly.
This needed an additional partial revert of https://github.com/rust-lang/rust/commit/5b08c9f39754039ef9c6cbde157ac9eb8c252a58 for changes that happened due to later cleanups.
I also added a test from the issue to make sure this actually fixes it 😆
r? `@wesleywiser` `@pnkfelix`
|
|
|
|
|
|
This reverts commit 2e7a201d2e9e73477f1e69240711bfe09aefdc18.
|
|
|
|
This lead to a miscompilation in at least `char::is_whitespace` and
probably in more unknown places.....
This reverts commit 684663ed380d0e6a6e135aed9c6055ab4ba94ac8.
|
|
|
|
|
|
For now this keeps all the configuration identical (AFAICT) but we'll
likely want to play with the specifics to move some of the slower
builders to larger machines and the faster builders to smaller machines,
likely reducing overall usage and improving CI times.
|
|
[beta-1.69-cargo] Backport GitHub RSA key revocation
1 commits in 7b18c85808a6b45ec8364bf730617b6f13e0f9f8..713164a40962a0a76c7f3ad8aafb6f03410e21d2
2023-03-17 12:29:33 +0000 to 2023-03-26 20:05:25 +0000
- [beta] Backport GitHub RSA key revocation (rust-lang/cargo#11892)
|
|
|
|
[beta-1.69] cargo beta backports
3 commits in 9880b408a3af50c08fab3dbf4aa2a972df71e951..7b18c85808a6b45ec8364bf730617b6f13e0f9f8
2023-02-28 19:39:39 +0000 to 2023-03-17 12:29:33 +0000
- [beta-1.69] backport rust-lang/cargo#11824 (rust-lang/cargo#11863)
- [beta-1.69] backport rust-lang/cargo#11820 (rust-lang/cargo#11823)
- chore: Backport rust-lang/cargo#11630 to `1.69.0` (rust-lang/cargo#11806)
r? `@ghost`
|
|
|
|
[beta] backport
This PR backports:
- #108901: fix: evaluate with wrong obligation stack
- #108754: Retry `pred_known_to_hold_modulo_regions` with fulfillment if ambiguous
- #108691: fix multiple issues when promoting type-test subject
It also bumps to the released stable.
r? `@Mark-Simulacrum`
|
|
|
|
|
|
|
|
|
|
Smarter and simpler!
|
|
Don't require a region to have an `external_name` in order to be
promoted.
|
|
|
|
|
|
|
|
|
|
[beta] Promote 1.69.0 nightly to beta
This bumps version placeholders and switches the CI channel.
https://forge.rust-lang.org/release/process.html#beta-to-stable
r? `@Mark-Simulacrum`
|
|
|
|
|
|
Don't call `temporary_scope` twice.
`mirror_expr_inner` calls `temporary_scope`. It then calls `make_mirror_unadjusted` which makes an identical call to `temporary_scope`.
This commit changes the `mirror_expr_inner` to get the `temp_lifetime` out of the expression produced by `make_mirror_unadjusted`, similar to how it currently gets the type.
r? `@cjgillot`
|
|
Rollup of 6 pull requests
Successful merges:
- #108298 (Fix ICE: check if snippet is `)`)
- #108405 (Lazily compute crate name for consider_optimizing)
- #108656 (Rustdoc search: Emit an error for unclosed generic)
- #108660 (Remove ne implementations from strings)
- #108669 (Allow checking whether a type allows being uninitialized)
- #108727 (rustc_expand: make proc-macro derive error translatable)
Failed merges:
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
rustc_expand: make proc-macro derive error translatable
kept this tiny so as to point to it as an example in rustc-dev-guide
`@rustbot` label +A-translation
|
|
Allow checking whether a type allows being uninitialized
This is useful for clippy ([rust-lang/clippy#10407](https://github.com/rust-lang/rust-clippy/issues/10407)) and for the future `MaybeUninit::assume_init` panics (#100423).
|
|
Remove ne implementations from strings
As far as I can tell, there isn't really a reason for those.
|
|
r=notriddle
Rustdoc search: Emit an error for unclosed generic
Now, search like `a<` will error as it should (and as written in the eBNF).
r? `@notriddle`
|
|
r=WaffleLapkin
Lazily compute crate name for consider_optimizing
The extra query is unnecessary in the common case of not having fuel.
|
|
Fix ICE: check if snippet is `)`
Fixes #107705
|
|
Remove `NormalizationError::ConstantKind`
No longer in use by `TryNormalizeAfterErasingRegionsFolder` (as of #102355 / e8150fa60cc445de7a57db634deb0668880be593 it seems). It's making `LayoutError`, etc. kinda large -- that was noticed by `@zoxc.`
|