[LowerToHW] Avoid "assert/assume/cover" string comparison, refactor label creation, NFC#10251
Open
[LowerToHW] Avoid "assert/assume/cover" string comparison, refactor label creation, NFC#10251
Conversation
6e2dc82 to
7db857f
Compare
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.
Stop using "assert/assume/cover" string to specify a kind. Also factored out label creation.
Alternatively I considered to use declarative trait-based abstraction (like below) but did't like it because of heavy usage of templates, though it's still unfortunate to see there are 4 different target ops.
Assisted-by: Codex: GPT 5.4