Skip to content
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

Clarify what iterating over operations means #510

Open
tobie opened this issue Jan 11, 2018 · 1 comment
Open

Clarify what iterating over operations means #510

tobie opened this issue Jan 11, 2018 · 1 comment

Comments

@tobie
Copy link
Collaborator

tobie commented Jan 11, 2018

In #494 (comment), @TimothyGu brought up the issue that operations have a many to one relationship with operation identifiers. That is, overloaded operations share a single identifier.

So when we say "iterate over the operations of interface |Foo|", what we really mean is something hand-wavy like: "iterate over the unique identifiers of the operations of interface |Foo| and consider the operations identified by a single identifier as a single but slightly special thing."

Do we need to be more specific, here?

@TimothyGu
Copy link
Member

This issue is really only specific to the JS binding chapter. In a language like C++, the current system makes total sense.

Because #432 is still an open issue I’m not too worried about the handwaviness at this moment. We can of course define a new term to explain why uniqueness is a requirement for these iterations but it’s reasonably unambiguous w.r.t. what it means as it is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants