Oops, I'm an idiot and didn't see this.
On 26/07/2017 21:49:11, Logan Smyth wrote:
There is currently an active proposal for this:
https://github.com/tc39/proposal-numeric-separator
[https://github.com/tc39/proposal-numeric-separator]
On Wed, Jul 26, 2017 at 1:47 PM, Alexan
Large number are hard to read in JavaScript, is 2384923842 over a billion? Or
just several hundred million. One solution to this some languages have used is
to allow underscores within numbers. You can immediately recognise
2_384_923_842 is a number in the billions, rather than millions.
It w
In which case, perhaps change this proposal to .slice(start, end, step)___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
> requires browser use
Nope. Both Discourse + NodeBB allow the ability to use them as a mailing list.
Thus, they require nothing more to use than the current system. (You require
a browser to sign up, but mailing lists here require the same thing as well).
> long term archival
I would argue
Thought I'd move the topic of a new communication tool to it's own thread. So
that it doesn't pollute the (already polluted) removal of language features
thread.
I took agree with Mark, I think it's time to move away from a mailing list and
the obvious choice for discussions like this is a for
new major revision of JS, which should not happen before a long
time.
* would it make more sense to start on js7 instead of js2
No, because ES6, ES7, ... are still JS 1.
From: Alexander Craggs [mailto:alexan...@debenclipper.com]
Sent: Tuesday, July 25, 2017 3:54 PM
To: doodad-js Admin ; e
I'm sorry, I missed that suggestion.
That definitely sounds significantly better than a new MIME type. Although two
thoughts I have are:
- How are you going to deal with scenarios that don't have extensions, e.g.
REPL or inline JS.
- Are extensions going to be released often, or is this goi
Some thoughts on using MIME types to distinguish between versions:
1. In terms of including it in
you think.
On Sat, Jul 22, 2017 at 10:19 PM, Alexander Craggs mailto:alexan...@debenclipper.com]> wrote:
(Apologies for the double email Jordan, I accidentally replied to just you, not
es-discuss as well. I'm new to this whole mailing list thing.)
Apologies, that was a bad example. I wa
mode simply ignore the no-op string.
There's lots of other threads on why no new modes are likely to ever be
introduced.
There's also no need to add pragmas or make breaking changes to make error
messages more useful; for that, I suggest filing specific suggestions on each
engine vendo
One of the main issues I've found with why a significant number of proposals
are rejected is because it would introduce breaking changes into JavaScript, a
language created over 22 years ago. It doesn't surprise me that people have
suggestions to improve JavaScript that are breaking, popular sy
I always found the Python methodology of selecting characters from strings (or
items from arrays) to be the most natural I've found among a number of language
solutions. Was considering whether adding the syntax would be beneficial for
JavaScript. For those who do not know, the syntax is as so
12 matches
Mail list logo