Naveen Chawla (2018-01-18T12:01:02.000Z)
naveen.chwl at gmail.com (2018-01-18T12:04:39.960Z)
I agree it's a misuse, my point is simply why introduce the possibility? Key question for me (for any feature): show how it can reduce the chances of bugs. Arrow functions succeed, for example: by removing nested "this" contexts, thereby simplifying moving of code around etc. Async await succeeds, for example: by linearizing and hence considerably simplifying the building and reading of asynchronous data flows in code. Classes succeed, for example: by removing the fiddly overhead in establishing (especially multi-level) inheritance using prototypes. The examples on the proposal page don't succeed, for me, in establishing how (if at all) using a do-expression could (vs the most elegant alternative currently), if not the converse.
naveen.chwl at gmail.com (2018-01-18T12:04:15.894Z)
I agree it's a misuse, my point is simply why introduce the possibility? Key question for me (for any feature): show how it can reduce the chances of bugs. Arrow functions succeed, for example: by removing nested "this" context, thereby simplifying moving of code around etc. Async await succeeds, for example: by linearizing and hence considerably simplifying the building and reading of asynchronous data flows in code. Classes succeed, for example: by removing the fiddly overhead in establishing (especially multi-level) inheritance using prototypes. The examples on the proposal page don't succeed, for me, in establishing how (if at all) using a do-expression could (vs the most elegant alternative currently), if not the converse.
naveen.chwl at gmail.com (2018-01-18T12:02:35.114Z)
I agree it's a misuse, my point is simply why introduce the possibility? Key question for me (for any feature): show how it can reduce the chances of bugs. Arrow functions succeed, for example: by removing nested "this" context, thereby simplifying moving of code around etc. Async await succeeds, for example: by linearizing and hence considerably simplifying the building and reading of asynchronous data flows in code. Classes succeed, for example: by removing the fiddly overhead in establishing (especially multi-level) inheritance using prototypes. The examples on the proposal page don't succeed, for me, in establishing how (if at all) using a do-expression could (vs the most elegant alternative currently), if not the converse.