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

Add support for [MapClass(type, type)]. #10

Merged
merged 3 commits into from
May 13, 2014

Conversation

tobie
Copy link
Member

@tobie tobie commented May 8, 2014

argument_list now return undefined when no arguments are found (rather than an empty array).

argument_list also backtracks its changes when it cannot find any arguments.

`argument_list` now return undefined when no arguments are found (rather than an empty array).

`argument_list` also backtracks its changes when it cannot find any arguments.
} else if (pair = type_pair()) {
// [MapClass(DOMString, DOMString)]
ret.typePair = pair;
} else {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please put both the elses above on their own lines?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And move the comment describing what they do right before them.

// does foo
else {
}

@darobin
Copy link
Member

darobin commented May 12, 2014

All good except the small stylistic issue.

darobin added a commit that referenced this pull request May 13, 2014
Add support for [MapClass(type, type)].
@darobin darobin merged commit 58bd9a9 into w3c:develop May 13, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants