make trait method resolution more exhaustive, fixes #1312 #1341
+29
−10
Conversation
This file contains 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
Chris-Hawblitzel
approved these changes
Nov 15, 2024
tjhance
force-pushed
the
trait-instance-checks
branch
from
1de2a2a
to
ca935a5
Compare
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.
Provide an 'unsupported' error for unsupported InstanceDef. This is consistent with the behavior for other unrecognized trait instances.
For example, trying to clone a tuple (which is currently unsupported) will now produce a not-supported error (at present, it will just fail to verify because Verus has no information about what tuple-cloning does; see #1312).