Conversation
Collaborator
|
This PR changes a file inside |
Collaborator
|
Thanks for the pull request, and welcome! The Rust Project has assigned @spastorino (or someone else) to review your changes, you should hear from them (or someone else) within the next two weeks. Please see the contribution instructions and our LLM policy for more information. Why was this reviewer chosen?The reviewer was selected based on:
|
This comment has been minimized.
This comment has been minimized.
imlazyeye
force-pushed
the
chore/fn-ptr-no-ice-test
branch
from
September 18, 2026 16:48
7226e6d to
811e4ae
Compare
Contributor
|
lgtm. split between the old/new solver tests seems consistent |
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
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.
Adds regression tests for #142717.
Like the issue says, the ICE is resolved on the new solver, but compiletest forces
-Znext-solver=coherencewhich will make it still occur. That's why the UI test hasgloballyto pin the fixed behavior but the crash test exists for the broken one.Let me know if both tests are not necessary/if this should indeed close that issue.
r? types