- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Feb 2025 22:11:24 +0000
- To: public-css-archive@w3.org
> if this position changes in the future would you be able to make that use of if make sense or would you be forced to pick a different keyword? As @benface said, nothing prevents us from adding `@if` in the future with whatever syntax we want. At-rules and functions are completely distinct. (Well, it turns out there *is* [a reason to avoid `@if`](https://github.com/w3c/csswg-drafts/issues/6684), but that's unrelated to this topic.) The syntax would definitely be an at-rule, because that's what's allowed at the rule level in CSS syntax. No chance of confusion with value-level functions. > The point that CSS is different is also well taken, so if a given keyword evokes certain expectations across many languages (again just focusing on points 2-4), shouldn't we find a different keyword? Not necessarily. Different languages express themselves differently. That's fine. "If" is by far the most common word for the basic conditional syntax across languages. This is the basic conditional syntax for CSS. It *also* doesn't look like any of the *less*-common conditional syntaxes in nearby languages, like "switch" or "cond" or "match", because those languages are also designing under their own assumptions and syntax precedents. > is the meaning of "empty token stream" defined anywhere in a spec? Tokens are discussed in CSS Syntax and, more relevantly for this topic, in CSS Variables. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10064#issuecomment-2679775348 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 24 February 2025 22:11:25 UTC