Clarify rules around IDL method arguments

speced / spec-dfn-contract

Contract for marking up definitions in specifications

1 stars 0 forks source link

Clarify rules around IDL method arguments #4

Open dontcallmedom opened 3 years ago

dontcallmedom commented 3 years ago

As discussed in https://github.com/w3c/reffy/issues/336#issue-644580671, bikeshed and respec aren't aligned as data producers nor as data consumers when it comes to including arguments in definitions. Some of the constraints around the topic are linked with overloaded methods, although the fact that they are now mandated to be defined in a single IDL fragment may help on the producer side.

dontcallmedom commented 3 years ago

Relevant bikeshed issue https://github.com/tabatkins/bikeshed/issues/1733

marcoscaceres commented 3 years ago

WebIDL says we should support the form foo(bar, bas) etc., so I'd be inclined to support that (and I agree it's better than what we have now in ReSpec)... just haven't gotten around to fully coding it up: https://github.com/w3c/respec/issues/3571