Fix operator resolution involving generics and supertypes #1424
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.
For a hypothetical operator defined as
the following should hold:
(System.Boolean, System.Any)
,OperatorB
should resolve with the(System.Boolean, System.Integer) -> System.Boolean
signature.(System.Boolean, System.Integer)
later during translation,OperatorB
should resolve with the(System.Boolean, System.Integer) -> System.Boolean
signature. Previous resolution involvingSystem.Any
must not affect this resolution.(FHIR.Quantity, System.Integer)
,OperatorB
should resolve with the(FHIR.Quantity, System.Integer) -> FHIR.Quantity
signature.(FHIR.Distance, System.Integer)
,OperatorB
should resolve with the(FHIR.Distance, System.Integer) -> FHIR.Distance
signature. Previous instantiation of(FHIR.Quantity, System.Integer)
with a supertype forOperatorB
must not affect this resolution.