Devils advocate: if you were to measure usage of identifiers named “and” or
“or”, on the web, how substantial do you think their use would be? And even if
they were used a fair bit, that hasn’t really stopped the introduction of other
contextual keywords in the past.
If you really wanted to, yo
This is a non-starter, as AND and OR are already valid identifiers.
On Tue, May 24, 2016 at 9:15 PM Francis Clavette
wrote:
> Hi,
> I’d like to be able to use AND for && and OR for || in conditional
> statements in a future version of ECMAScript. It’s a feature I’ve always
> been wanting since t
Even with some larger libraries, you can do things like this:
```js
// small modules
import xmlParse from 'xml/parse';
import xmlCreate from 'xml/create';
import xmlSandwich from 'xml/sandwich';
import jsonParse from 'json/parse';
import jsonCreate from 'json/create';
import jsonBacon from 'json
Closing the loop on this: this proposal is now stage 4, and will be
included in ES 2017. https://github.com/tc39/ecma262/pull/582
Polyfill: https://www.npmjs.com/package/object.getownpropertydescriptors
On Wed, Jan 20, 2016 at 9:26 PM, Jordan Harband wrote:
> If Rick is unavailable, and after I
* sorry, to clarify: This was discussing padding. trimLeft/trimRight /
trimStart/trimEnd is still stage 2
On Wed, May 25, 2016 at 2:56 PM, Jordan Harband wrote:
> Closing the loop on this: this feature is now stage 4, and will be
> included in ES 2017. https://github.com/tc39/ecma262/pull/581
>
Closing the loop on this: this feature is now stage 4, and will be included
in ES 2017. https://github.com/tc39/ecma262/pull/581
Polyfills: https://www.npmjs.com/package/string.prototype.padstart and
https://www.npmjs.com/package/string.prototype.padend
On Thu, Jul 30, 2015 at 10:33 AM, Behrang S
Closing the loop on this: this proposal is now stage 4 and will be included
in ES 2017. https://github.com/tc39/ecma262/pull/581
On Mon, Jan 11, 2016 at 11:40 PM, Norbert Lindenberg <
ecmascr...@lindenbergsoftware.com> wrote:
> Thank you for renaming padLeft/padRight to padStart/padEnd.
>
> On th
Are lines 149-164 the part you want people to look at?
On May 23, 2016 4:47 PM, "Geoffrey Garen" wrote:
> Hi folks.
>
> ECMA-402 lists default locale as an unspecified "implementation dependent
> behaviour”.
>
> In the absence of a specified default locale behavior, can we agree to a
> de facto o
> Le 25 mai 2016 à 03:29, kdex a écrit :
>
> IMHO, the current operators `&&`, `&`, `||` ,`|` are the cleanest
> implementation of `and` and `or` that I could think of.
I don’t think so: It is not ideal that the longest forms, `&&` and `||`, are by
far the most current ones. But this is histo
It's not feasible anyway because AND and OR are already valid identifiers:
a = foo()
&&(bar)
is equivalent to `a = foo() && bar`, but
a = foo()
AND(bar)
is equivalent to
a = foo();
AND(bar);
On Wed, 25 May 2016 at 02:29 kdex wrote:
> Could you explain how your second example is cleaner?
Small modules are great, especially for creators. I’m onboard with
small-modules being the default and recommended way of doing things.
But.. I think history has shown that there is a use-case and a place in the
world for larger composed modules. Take a look at lodash or jQuery for example.
From
11 matches
Mail list logo
