Re: [csswg-drafts] [css-mixins] Should `result` be mandatory in `@function`? (#10562)

The CSS Working Group just discussed ``[css-mixins] Should `result` be mandatory in `@function`?``, and agreed to the following:

* `RESOLVED: result is optional in @function`

<details><summary>The full IRC log of that discussion</summary>
&lt;kbabbitt> TabAtkins: the question raised here is should the result descriptor be mandatory in @function rule<br>
&lt;kbabbitt> ... result describes what function returns<br>
&lt;kbabbitt> ... is it strictly required to have it, or can it be omitted with reasonable default behavior<br>
&lt;kbabbitt> ... thread is leaning towards it should be optional<br>
&lt;kbabbitt> ...IACVT if there isn't one<br>
&lt;kbabbitt> ... matches up with other languages concepts of optional<br>
&lt;kbabbitt> ... at the moment you have to indirect through a custom property to use this value instead if IACVT<br>
&lt;kbabbitt> ... we have other proposals to make that easier<br>
&lt;kbabbitt> ... unless there's a great reason to require it, we think it's fine to let it be omitted<br>
&lt;kbabbitt> ... and have it be IACVG when that hits<br>
&lt;kizu> +1 to be optional<br>
&lt;kbabbitt> s/IACVG/IACVT/<br>
&lt;lea> q?<br>
&lt;miriam> +1<br>
&lt;lea> q+<br>
&lt;kbabbitt> astearns: other opinions/questions?<br>
&lt;astearns> ack lea<br>
&lt;kbabbitt> lea: if result is mandatory does that mean rule is tropped at parse iyme if it's missing?<br>
&lt;kbabbitt> TabAtkins: yes<br>
&lt;kbabbitt> lea: might be use cases to add later? could just have dummy one<br>
&lt;kbabbitt> Proposed: result is optional in @function<br>
&lt;kbabbitt> RESOLVED: result is optional in @function<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10562#issuecomment-2622876514 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 21:19:46 UTC