| 03:56 | <rbuckton> |
using proposal and was pulled out to serve as a broader independent proposal. |
| 03:59 | <Jessidhia> | Discards in array binding and assignment patterns (i.e., const [void, a, void] = iter) to explicitly mark elisions and avoid trailing , confusion ([a, ,]). amusingly there is a comma confusion here (should be [, a,]) |
| 08:26 | <Jack Works> | working on simple Go To Definition functionality |
| 09:44 | <Domenic> | The proposal-void-binding is compelling in how it lists lots of cases where this would be moderately useful. Still, for the original case of using, using void = new UniqueLock(mutex) feels sadly lame, compared to using new UniqueLock(mutex). I think because, unlike cases such as parameter bindings or destructuring, I'm not trying to express "don't put anything in this slot"; I'm actually trying to avoid the "slot" (binding) concept at all, and just say "I am using this resource". |
| 09:46 | <Domenic> | So to me it feels like a tradeoff between trying to create a generally useful void-binding concept, versus making the using-a-resource case more idiomatic with specialized syntax like using! expression or something else. Since it's maybe not possible to create something both unambiguous and not-super-weird-looking, I guess using void = is probably the best place to end up. Still sad. |