| 01:12 | <Anthony Bullard> | For anyone interested in (). I spent about 5 minutes right now on my phone thinking about it, so please be kind if I’m forgetting something obvious. |
| 01:15 | <Anthony Bullard> | That syntax is used for the Unit type in functional languages, so might make some intuitive sense, it’s not an operator, and should be unambiguous in all binding contexts, including pattern matching and extractors |
| 01:39 | <rbuckton> | () is not an option. One of the major motivators for discards is using declarations, and using() = foo would be interpreted as an Extractor in an assignment pattern, and it's already interpreted as an illegal assignment to a call expression. |
| 01:40 | <rbuckton> | See https://github.com/tc39/proposal-discard-binding/issues/10 |
| 01:58 | <Anthony Bullard> | See https://github.com/tc39/proposal-discard-binding/issues/10 |
| 02:03 | <Anthony Bullard> | Also, can I say I wish we could have eliminated space separated call syntax in strict mode at least. I’ve never understood the argument for it |
| 02:17 | <Michael Ficarra> | are there any languages that use postfix parens for function calls and don't allow spaces in all the same spots we do? |
| 02:18 | <Michael Ficarra> | while I don't think you should format your code like that, I think it would be very strange from a parser perspective to disallow it |
| 02:30 | <Anthony Bullard> | are there any languages that use postfix parens for function calls and don't allow spaces in all the same spots we do? |
| 02:33 | <Anthony Bullard> | I guess I am forgetting about Allman style C |