Timothy Johnson (2018-11-10T17:48:59.000Z)
timothy at idioticdev.com (2018-11-10T18:01:10.160Z)
I'm putting together a proposal for a cascade operator like the one in dart. I think it fits the javascript design space quite well. The popularity of method chaining APIs points to this being something the javascript community wants. For example foo ..a.b = c ..d() Would be equivalent to foo.a.b = c; foo.d() Or more accurately (obj => { obj.a.b = c; obj.d(); return obj; })(foo) The full proposal is at https://github.com/RedHatter/proposal-cascade-operator. Any thoughts? Also, how do I go about getting this accepted at stage 0? Edit: Fixed the formatting, sorry.
timothy at idioticdev.com (2018-11-10T17:57:17.353Z)
I'm putting together a proposal for a cascade operator like the one in dart. I think it fits the javascript design space quite well. The popularity of method chaining APIs points to this being something the javascript community wants. For example foo..a.b = c..d() Would be equivalent to foo.a.b = c; foo.d() Or more accurately (obj => { obj.a.b = c; obj.d(); return obj; })(foo) The full proposal is at https://github.com/RedHatter/proposal-cascade-operator. Any thoughts? Also, how do I go about getting this accepted at stage 0? Edit: Fixed the formatting, sorry.
timothy at idioticdev.com (2018-11-10T17:54:36.995Z)
I'm putting together a proposal for a cascade operator like the one in dart. I think it fits the javascript design space quite well. The popularity of method chaining APIs points to this being something the javascript community wants. For example foo ..a.b = c ..d() Would be equivalent to foo.a.b = c foo.d() Or more accurately (obj => { obj.a.b = c obj.d() return obj })(foo) The full proposal is at https://github.com/RedHatter/proposal-cascade-operator. Any thoughts? Also, how do I go about getting this accepted at stage 0? Edit: Fixed the formatting, sorry.