- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Feb 2024 19:01:06 +0000
- To: public-css-archive@w3.org
> > would it help if they just used a different syntax so they couldn't easily be confused? > > I really liked the idea to recall the arguments via `arg(--foo)` — this way they won't conflict with the variables. Also: what if by separating them and making sure arguments resolve before variables, we could allow doing things like `var(arg(--foo))`? Was dreaming about something like this for a while. I think a common workflow for mixins is to start developing CSS normally, then copy certain code into a mixin. Using a separate syntax makes this higher friction. > Other than conditions, a thing to really consider when talking about mixins and functions is an ability to retrieve values from lists and maps. If there was an ability to define all the tokens as a single (or several) map or record, the downsides for the `using` could be much smaller, as you could just put the whole map there (even though I still not sure if there is any _use_ for it). While we do need maps and records, any solution that affects the definition of the data is a no-go for abstractions written by other parties than the page author. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9938#issuecomment-1961840800 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 February 2024 19:01:07 UTC