-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[openCypher tck case] empty list bug #2699
Comments
If we support empty list, maybe we should support empty set and empty map too, but:
empty set and empty map are in the same format so they're conflicted in the parser. |
where is the definition of set in opencypher tck? |
cypher doesn't support set. But we support set. |
If you try to add a new concept, add some set tck cases like the map/list cases in opencypher tck feature files. So, we can discuss whether the set behavior is proper and compatible with opencypher's list and map. Both lists and maps have a lot of behavior definitions and specifications. So I don't think adding a new concept is as easy as we expect. |
I agree, there are a lot of incompatible syntaxes |
IMO, |
IMO, set in not necessary. Why, Cypher, has no concept set, in about ten years. |
ACK. |
The text was updated successfully, but these errors were encountered: