| 11:45 | <canadahonk> | I think I don't have perms to edit the repo metadata for https://github.com/tc39/proposal-math-clamp, could I get perms for that (or could someone update the link to tc39.es)? ty |
| 14:26 | <ljharb> | fixed! |
| 18:42 | <jschoi> | like, it's already gotta be pretty confusing for anybody not paying close attention, and it'll get even more confusing once MDN et al. are in the mix But I’ve accepted that the repository name should be left alone. I just need to make sure MDN names with the shorter name it if it ever reaches Stage 3… |
| 18:44 | <jschoi> | no, we shouldn't change the name, we should just avoid naming proposals after specific API names in the first place (Autocorrection changed it on my phone just now to “proposal-upset”, which might be as good of a name as any.) |
| 18:45 | <jschoi> | I watch very carefully for this mistake during advancement to Stage 1, and so should you |
| 18:47 | <Michael Ficarra> | the more general advice is "don't overcook your Stage 1 proposal", and choosing a name that's not tied to a particular solution follows from that |
| 18:52 | <Michael Ficarra> | ironically, "map get-or-insert" would probably be it, though "upsert" isn't the worst since it means that same thing to many people, it's just not universally known and not self-evident to those who don't know it |
| 22:34 | <bakkot> | shu: I assume you've seen https://github.com/WebAssembly/custom-descriptors/blob/main/proposals/custom-descriptors/Overview.md |
| 22:34 | <bakkot> | some bearing on the structs proposal, maybe |
| 22:48 | <Michael Ficarra> | @bakkot it was presented at the wasm CG yesterday (and advanced!) and both Shu and I were there |
| 23:18 | <shu> | bakkot: yes, thomas is a colleague |
| 23:19 | <bakkot> | good good |