Re: Function composition vs pipeline
How is either operator not "a different way of calling functions"? On Thu, Feb 22, 2018 at 8:34 PM, Naveen Chawlawrote: > I was just thinking about the relative merits and coexistence (or not) of > function composition operator and function pipeline operator features: > > e.g. > https://github.com/TheNavigateur/proposal-pipeline-operator-for- > function-composition > https://github.com/tc39/proposal-pipeline-operator > > They can of course co-exist, but there is overlap only in the respect that > both allow function pipelines to be called from left to right (except the > input parameter in the case of the composition feature, which requires > existing bracket syntax to be used to call it). If one were to be chosen, > would say that a function composition operator adds a whole new dimension > of expressive power to the language, whereas a pipeline operator only > offers a different way of calling functions. > > I was wondering about all of your thoughts about whether you'd prefer only > the pipeline operator, only the composition operator, or both, or neither > to be added to the language (these are pretty much all the possibilities), > and why. > > ___ > es-discuss mailing list > es-discuss@mozilla.org > https://mail.mozilla.org/listinfo/es-discuss > > ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
Function composition vs pipeline
I was just thinking about the relative merits and coexistence (or not) of function composition operator and function pipeline operator features: e.g. https://github.com/TheNavigateur/proposal-pipeline-operator-for-function-composition https://github.com/tc39/proposal-pipeline-operator They can of course co-exist, but there is overlap only in the respect that both allow function pipelines to be called from left to right (except the input parameter in the case of the composition feature, which requires existing bracket syntax to be used to call it). If one were to be chosen, would say that a function composition operator adds a whole new dimension of expressive power to the language, whereas a pipeline operator only offers a different way of calling functions. I was wondering about all of your thoughts about whether you'd prefer only the pipeline operator, only the composition operator, or both, or neither to be added to the language (these are pretty much all the possibilities), and why. ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
Re: Re: Async Class
"why a static factory" And more notes: "return img" - this is cut version In my example you get obj - not image. And my sample was simple. I hope not so long left to class private var + decorators And sample can be then more complex with it: async class Class{ @some_decorator static private method(){} static var = some_var } and have not onle one Extends Class ExtClass ExtExtClass Maybe i try to force events, but time never waits... ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss