-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect tuple equality behavior #1349
Comments
Are you certain this should be
No mention of "null". The discussion for Codes and Concepts says it uses "tuple semantics" and the example shown implies it would be false, not null.
define "Code1": Code { system: 'http:https://loinc.org', code: '8480-6', version: '1.0', display: 'Systolic blood pressure' }
define "Concept1": Concept { codes: { Code1 }, display: 'Concepts' }
define "Concept2": Concept { codes: { Code1 }, display: 'More Concepts' }
define "EqualIsTrue": Code1 = Code1
define "EqualIsFalse": Concept1 = Concept2 Notice how |
This expression currently returns false:
But tuples have no implied ordering, so this should be
null
Test cases for this (and other tuple equality testing) are being considered for the cql-tests repository here:
cqframework/cql-tests#3
When those tests are agreed and approved, they should be used as the source for the test for this issue
The text was updated successfully, but these errors were encountered: