Re: Re: The "Pipeline" Operator - Making multiple function calls look great

Sidebar: thanks to Isiah Meadows, the FBS proposal now also supports constructor wrapping via the `::new` syntax: let factory = SomeClass::new; On Mon, Dec 14, 2015 at 9:00 AM Marius Gundersen wrote: > Do we really need to add support for await in a pipeline syntax

Re: Re: The "Pipeline" Operator - Making multiple function calls look great

`await` could be handled by with contextual lexing: handling `|> await` as a single keyword. Another solution would be to collapse the two into a variant of the pipeline operator: `|await>`, `|!>`, ... This could be an opportunity to revive the syntax sugar that was proposed in

caps lock state

Hi! There is no way to determine the actual state of a caps lock key. I would like to request an enhancement of the event object to include the caps lock state: ```js document.addEventListener( 'keydown', function( event ) { if ( event.capsLock ) { alert( 'caps lock on!' ); } }); ```

Re: The "Pipeline" Operator - Making multiple function calls look great

On Sun, Dec 13, 2015 at 10:32 PM, Kevin Smith wrote: > (someArray > .filter(...) > .map(...) > |> someOtherArrayOp > ).forEach(...) > > Note the extra parens before the "forEach" invocation. For the record I think a pipe operator is silly - I wish | were available