Fix ICE in next-solver TransmuteFrom candidate#154991
Merged
rust-bors[bot] merged 1 commit intorust-lang:mainfrom Apr 9, 2026
Merged
Fix ICE in next-solver TransmuteFrom candidate#154991rust-bors[bot] merged 1 commit intorust-lang:mainfrom
rust-bors[bot] merged 1 commit intorust-lang:mainfrom
Conversation
rustbot
added
S-waiting-on-review
Collaborator
|
r? @JohnTitor rustbot has assigned @JohnTitor. Use Why was this reviewer chosen?The reviewer was selected based on:
|
Member
|
r? me @bors r+ rollup |
Contributor
rust-bors
bot
added
S-waiting-on-bors
Member
rust-bors
bot
added
S-waiting-on-author
Contributor
|
🚧 Squashing... this can take a few minutes. |
Contributor
|
❗ Failed to push the squashed commit to |
Member
|
can you please squash commits if possible |
Treat TransmuteFrom goals with non-region inference variables as ambiguous before running transmutability, instead of computing layouts for unresolved types. The old solver already treated these goals as ambiguous, so only the next solver could hit this ICE.
cijiugechu
force-pushed
the
fix/next-solver-transmutefrom-ice
branch
from
c3c154f to
ee135be
Compare
Contributor
Author
Squashed. |
Member
|
@bors r+ rollup |
Contributor
rust-bors
bot
added
S-waiting-on-bors
rust-bors bot
pushed a commit
that referenced
this pull request
Apr 9, 2026
Rollup of 10 pull requests Successful merges: - #150316 (Do not use non-wf input expectations from fudge when checking function calls) - #152859 (`-Znext-solver` use the trait object's own bounds instead of goal when considering builtin object bounds) - #154856 (Fix linking two dylibs together when both depend on profiler_builtins) - #153888 (Avoid stack overflow in FindExprBySpan) - #154991 (Fix ICE in next-solver TransmuteFrom candidate) - #154995 (min/max_by tests: also check result) - #155004 (core/num: Fix feature name for unstable `integer_extend_truncate` functions) - #155007 (renaming method is_impl_trait to is_opaque) - #155009 (meta: Add checkboxes to unsresolved questions in issue templates) - #155017 (Update tracking issue number of future-incompatibility lint `unstable_syntax_pre_expansion`)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Treat TransmuteFrom goals with non-region inference variables as ambiguous before running transmutability, matching the old solver.
Closes #153370 .