-
Notifications
You must be signed in to change notification settings - Fork 20
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
"Union" could have more description, and maybe a new name #21
Comments
Good point. We have yet to decide whether unions remove or preserve duplicates and I think the outcome of that decision should influence the naming. "Union" as you point out has a set theory connotation and implies removing duplicates. It's tricky though because I think the result is ordered, whereas sets aren't ordered. |
Regarding duplicates specifically, please see #23. |
Not much actionable discussion here. |
Clarify related text; add explanation of change. Take slice-selector apart to define slice-index. Close #21.
The term "union" will likely be unfamiliar for readers (it is for me) and could use a bit more description than "A union
matcherselector consists of one or more union elements.""Union" isn't a common term outside of set manipulation. I would call the
[...]
an "indexer," which is a much more well-known term and is already associated with this construct in many programming languages. The values inside are indices (as opposed to "union children" or "union elements"), of which there are multiple types:See selector query expressions for more details on the query-style indexers.
The text was updated successfully, but these errors were encountered: