-
Notifications
You must be signed in to change notification settings - Fork 15
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
Items before etc #177
Items before etc #177
Conversation
…nding-where; and drop range-to and range-from
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In items-starting-where
, the first example is:
The expression fn:items-starting-where(10 to 20, ->{. gt 12}) returns 13, 14, 15, 16, 17, 18, 19, 20.
I think it would be more consistent to say it returns (13, 14, ..., 20)
with parenthesis to indicate that it's a sequence. Also for the last example, (<h2/>,<img/>)
Was the addition of fn:op
in this PR intentional?
I see what happened with |
Also: you've added |
I found myself with a GIT conflict, and fn:op found it's way in because I'm not very good at managing GIT conflicts. Sorry!
Michael Kay
… On 5 Oct 2022, at 09:45, Norman Walsh ***@***.***> wrote:
Also: you've added fn:op to the function catalog, but you haven't referenced it from the specification itself, so it doesn't appear.
—
Reply to this email directly, view it on GitHub <#177 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASIQIVEEV6N6JTXTD646CTWBU53RANCNFSM6AAAAAAQ4Y4D5Y>.
You are receiving this because you authored the thread.
|
Proposal: #149 |
Resolved by #199, I believe. |
No description provided.