ES RegExp processor

2017-04-15 Thread Dmitry Soshnikov
(this is mostly an FYI post on JS regexes processing tool) Recently I've been posting about ES RegExp parser[1], which eventually got evolved into a generic ES RegExp processor (called `regexp-tree`). This can be used for different kinds of purposes, and regarding ECMAScript spec -- it can be

Re: FW: Re: Strict Relational Operators

2017-04-15 Thread Matthew Robb
Also there was once the is/isnt operators and they lasted in ES6 for a very long time and went pulled for reasons like this. On Apr 15, 2017 4:06 AM, "Isiah Meadows" wrote: > Okay, I stand corrected... (I forgot about those) > > On Sat, Apr 15, 2017, 04:01 Jordan Harband

Re: Re: Strict (non-coercing) expressions

2017-04-15 Thread Bruno Jouhier
I don't know the ins and outs of the "nobody likes", I'll just respond as a "language user". We do not expect `NaN` in 99.99% of our code, and we do not expect infinities in 99.95% of it. Instead of having these values creep unnoticed though the computations (and else branches executed because

Re: FW: Re: Strict Relational Operators

2017-04-15 Thread Isiah Meadows
Okay, I stand corrected... (I forgot about those) On Sat, Apr 15, 2017, 04:01 Jordan Harband wrote: > There's also `instanceof`. > > On Fri, Apr 14, 2017 at 11:31 PM, T.J. Crowder < > tj.crow...@farsightsoftware.com> wrote: > >> Happy with `neq`. >> >> > Up to date, the only

Re: FW: Re: Strict Relational Operators

2017-04-15 Thread Jordan Harband
There's also `instanceof`. On Fri, Apr 14, 2017 at 11:31 PM, T.J. Crowder < tj.crow...@farsightsoftware.com> wrote: > Happy with `neq`. > > > Up to date, the only keyword > > operators have been exclusively unary, such as `typeof`, `await`, > > and `yield`. > > Not quite. :-) As I mentioned when

Re: FW: Re: Strict Relational Operators

2017-04-15 Thread T.J. Crowder
Happy with `neq`. > Up to date, the only keyword > operators have been exclusively unary, such as `typeof`, `await`, > and `yield`. Not quite. :-) As I mentioned when suggesting them originally, there is *one* binary non-symbolic operator already: `in` ```js if ("foo" in obj) ``` So the