- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 Feb 2021 17:49:39 +0000
- To: public-css-archive@w3.org
Yeah, setlike should only be used if object identity is sufficient for membership. (Or, if a derived key is instead used for uniqueness, adding something else with the same derived key causes replacement, but that's treading on thin ice.) If uniqueness depends on a derived key *and* replacement isn't allowed, then it's not a setlike at all, it's a registration map with write-once semantics, and should be a maplike. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5910#issuecomment-771036133 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 1 February 2021 17:49:41 UTC