Scotty Jamison

I'm actually not so sure that these two proposals will co-exist very well. What's the benefit of doing `array::removeNullish()` instead of `removeNullish(array)`? Well, I suspect it's the same reason why...

OK, I can understand that usage. Though, if I understand the current iteration of this proposal, there's still a couple of bumps for that use case. I believe you have...

I just found @js-choi's bind proposal repo - from what I understand, there's plans to present that one soon. I do like that proposal repo a little better - it...

Ahh, the fact this proposal "has a separate namespace" is a nonstarter, not that the function.call syntax not having a separate namespace is a nonstarted - got it :) I...

Currently, right before the break of a labeled block, are you allowed to place bizarre things like if-without-else? Or is that statement still susceptible to the rules?

I think the `updatePassword()` example above illustrates the issue best. As the do expression proposals currently stand, you can not write that example in its current form. It would be...

So, I guess in a nutshell: There are valid reasons someone may want to place a for loop, or if-without-else, etc, at the end of the do block - and...

> A do block inside a match expression inside a for loop would not necessarily have the same syntax restrictions as a do block directly does. That's a problem for...

Out of curiosity, what exactly do you feel is "exceedingly rare"? And perhaps I'll focus on async do blocks here. 1. The use of async do blocks in general? (I...

I kind of like it spelled out. But, I think that's mostly because I see and use it in its long-form more often than its short form, so that's what...