Revert performing basic const checks in typeck on stable#154930
Revert performing basic const checks in typeck on stable#154930rust-bors[bot] merged 1 commit intorust-lang:mainfrom
Conversation
|
This PR changes a file inside |
|
r? @chenyukang rustbot has assigned @chenyukang. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
@bors r=chenyukang |
…yukang Revert performing basic const checks in typeck on stable Revert rust-lang#149375, it caused a (desirable, but unintended) change where we now emit errors about constants in dead code. This was due to mir never seeing dead code, so no const checks being run on it. But typeck sees all written code and will check it. We'll land this again, with a proper types FCP and everything fixes rust-lang#153765 see [#t-types/nominated > rust-lang#153765: 1.95 beta regression: trait method calls in dead c…](https://rust-lang.zulipchat.com/#narrow/channel/326866-t-types.2Fnominated/topic/.23153765.3A.201.2E95.20beta.20regression.3A.20trait.20method.20calls.20in.20dead.20c.E2.80.A6/with/580203072) for discussions
…yukang Revert performing basic const checks in typeck on stable Revert rust-lang#149375, it caused a (desirable, but unintended) change where we now emit errors about constants in dead code. This was due to mir never seeing dead code, so no const checks being run on it. But typeck sees all written code and will check it. We'll land this again, with a proper types FCP and everything fixes rust-lang#153765 see [#t-types/nominated > rust-lang#153765: 1.95 beta regression: trait method calls in dead c…](https://rust-lang.zulipchat.com/#narrow/channel/326866-t-types.2Fnominated/topic/.23153765.3A.201.2E95.20beta.20regression.3A.20trait.20method.20calls.20in.20dead.20c.E2.80.A6/with/580203072) for discussions
…yukang Revert performing basic const checks in typeck on stable Revert rust-lang#149375, it caused a (desirable, but unintended) change where we now emit errors about constants in dead code. This was due to mir never seeing dead code, so no const checks being run on it. But typeck sees all written code and will check it. We'll land this again, with a proper types FCP and everything fixes rust-lang#153765 see [#t-types/nominated > rust-lang#153765: 1.95 beta regression: trait method calls in dead c…](https://rust-lang.zulipchat.com/#narrow/channel/326866-t-types.2Fnominated/topic/.23153765.3A.201.2E95.20beta.20regression.3A.20trait.20method.20calls.20in.20dead.20c.E2.80.A6/with/580203072) for discussions
|
@bors try jobs=x86_64-gnu-llvm-21-3 |
This comment has been minimized.
This comment has been minimized.
Revert performing basic const checks in typeck on stable try-job: x86_64-gnu-llvm-21-3
|
@bors r- |
|
This pull request was unapproved. This PR was contained in a rollup (#154953), which was unapproved. |
|
💔 Test for 44ed07e failed: CI. Failed job:
|
This comment has been minimized.
This comment has been minimized.
|
Wait for #154609 before reapproving this because of soft conflicts independently from the problem above |
It has merged, this PR can land now. |
fe1e292 to
d37d2be
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
@bors r=chenyukang |
|
@bors p=1 beta nominated backport |
|
beta backport approved as per compiler team on Zulip. A backport PR will be authored by the release team at the end of the current development cycle. Backport labels are handled by them. |
just noting: a backport PR is already open in #155033, but we haven't removed the nomination label yet. |
[beta] reverts and backports This reverts two `dbg!` changes to avoid regressions[^1][^2] in the upcoming 1.95 release: - std: avoid tearing `dbg!` prints #149869 - don't drop arguments' temporaries in `dbg!` #154074 - ... which was previously backported in #154725 This also reverts a stabilization over a late issue[^3] of semantics: - Stabilize `assert_matches` #137487 And a few other backport/reverts from `main`: - Revert performing basic const checks in typeck on stable #154930 / #155033 - Revert "`-Znext-solver` Remove the forced ambiguity hack from search graph" #154712 - Clarify that core::range ranges do not have special syntax #155002 [^1]: #153850 [^2]: #154988 [^3]: #154406
Rollup merge of #154930 - oli-obk:revert-const-check, r=chenyukang Revert performing basic const checks in typeck on stable Revert #149375, it caused a (desirable, but unintended) change where we now emit errors about constants in dead code. This was due to mir never seeing dead code, so no const checks being run on it. But typeck sees all written code and will check it. We'll land this again, with a proper types FCP and everything fixes #153765 see [#t-types/nominated > #153765: 1.95 beta regression: trait method calls in dead c…](https://rust-lang.zulipchat.com/#narrow/channel/326866-t-types.2Fnominated/topic/.23153765.3A.201.2E95.20beta.20regression.3A.20trait.20method.20calls.20in.20dead.20c.E2.80.A6/with/580203072) for discussions
[beta] reverts and backports This reverts two `dbg!` changes to avoid regressions[^1][^2] in the upcoming 1.95 release: - std: avoid tearing `dbg!` prints #149869 - don't drop arguments' temporaries in `dbg!` #154074 - ... which was previously backported in #154725 This also reverts a stabilization over a late issue[^3] of semantics: - Stabilize `assert_matches` #137487 And a few other backport/reverts from `main`: - Revert performing basic const checks in typeck on stable #154930 / #155033 - Revert "`-Znext-solver` Remove the forced ambiguity hack from search graph" #154712 - Clarify that core::range ranges do not have special syntax #155002 Clippy is backporting 2 ICE fixes and 1 perf regression (via #155051): - rust-lang/rust-clippy#16685 already backported in #154211 to stable. This makes sure that it doesn't regress again in beta/next stable - rust-lang/rust-clippy#16659 The ICE that is being fixed here was introduced in the 1.95 release cycle - rust-lang/rust-clippy#16652 Perf regression introduced in the 1.95 release cycle. [^1]: #153850 [^2]: #154988 [^3]: #154406
Revert #149375, it caused a (desirable, but unintended) change where we now emit errors about constants in dead code. This was due to mir never seeing dead code, so no const checks being run on it. But typeck sees all written code and will check it.
We'll land this again, with a proper types FCP and everything
fixes #153765
see #t-types/nominated > #153765: 1.95 beta regression: trait method calls in dead c… for discussions