fix logic for dcEqIgnoreDistinct
in sameType
#24197
Merged
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.
fixes #22523
There were 2 problems with the code in
sameType
fordcEqIgnoreDistinct
:{tyDistinct, tyGenericInst}
only ran if the given types had different kinds. This is fixed by always performing this skip.tyGenericInst
s have different values still ran fordcEqIgnoreDistinct
since it checks if the given types are generic insts, not the skipped types (and also only the 1st given type). This is fixed by only invoking this block fordcEq
;dcEqOrDistinctOf
(which is unused) also skips the first given type. Arguably there is another issue here thatskipGenericAlias
only ever skips 1 type.These combined fix the issue (
T
isGenericInst(V, 1, distinct int)
andD[0]
isGenericInst(D, 0, distinct int)
).#24037 shouldn't be a dependency but the diff follows it.