Re: [csswg-drafts] [css-functions-mixins] Handling superfluous arguments (#11190)

The CSS Working Group just discussed `[css-functions-mixins] Handling superfluous arguments`, and agreed to the following:

* `RESOLVED: If you have a function call with too many arguments, it's invalid`

<details><summary>The full IRC log of that discussion</summary>
&lt;miriam> go for it<br>
&lt;kbabbitt> TabAtkins: question raised, what to do if more arguments passed than defined<br>
&lt;kbabbitt> ... is this invalid, are arguments ignored, or something else<br>
&lt;kbabbitt> ... some discussion back and forth in issue, conclusion we're coming to is to make variable-arity part of validity of function call<br>
&lt;kbabbitt> ... so invalid call if wrong number of arguments passed<br>
&lt;kbabbitt> ... if we want to do variable-arity functions we can do that more explicitly<br>
&lt;kbabbitt> ... unless anyone has a good argument for doing something else with too many arguments, we'll stick with plan in the issue<br>
&lt;kbabbitt> ... which is to make it an invalid function call<br>
&lt;kbabbitt> astearns: comments/questions?<br>
&lt;kizu> +1<br>
&lt;kbabbitt> Proposed: If you have a function call with too many arguments, it's invalid<br>
&lt;miriam> +1<br>
&lt;kbabbitt> RESOLVED: If you have a function call with too many arguments, it's invalid<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11190#issuecomment-2623120139 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 29 January 2025 23:05:19 UTC