11.3.3 Intl.NumberFormat.prototype.format
Step 2: Remove colon
Step 2.a.i: Omit "then"
Step 2.a.iv: Omit "the result of"
Step 2.b: Missing .length (and .name property) for bound function (cf. bug 4288)
Step 2.a: Move to separate section? (cf. bug 4288)
---
11.3.3.1 NumberFormat Format Functions
A NumberFormat format function is an anonymous function that takes one argument value, and performs the following steps:
1. Let nf be the this value.
2. Assert: Type(nf) is Object and nf has an [[initializedNumberFormat]] internal slot whose value is true.
3. If value is not provided, let value be undefined.
4. Let x be ToNumber(value).
5. ReturnIfAbrupt(x).
6. Return FormatNumber(nf, x).
---
==========
FormatNumber abstract operation
Step 7: Remove colon
==========
ToRawPrecision abstract operation
Step 8.b: Remove colon
==========
ToRawFixed abstract operation
Step 7: Remove colon
> Step 2: Remove colon
> Step 2.a.i: Omit "then"
These are remnants of 1st Edition. Today was the deadline and removing colons and the word "then" in a panic all night is not a good use of anyone's time.
> Step 2.b: Missing .length (and .name property) for bound function (cf. bug 4288)
> Step 2.a: Move to separate section? (cf. bug 4288)
> 11.3.3.1 NumberFormat Format Functions
...
Added
(In reply to Rick Waldron from comment #1)
> > Step 2: Remove colon
> > Step 2.a.i: Omit "then"
>
> These are remnants of 1st Edition. Today was the deadline and removing
> colons and the word "then" in a panic all night is not a good use of
> anyone's time.
Sure, I understand that. That's just minor nit-picking to align the style with ES2015, but it's totally up to you if you want to mimic Allen's style from ES2015. You're the editor of the ECMA-402 spec, so I'm also ok if you prefer a different style or if you say you don't care about these things. (TBH, actually I don't even care about most editorial issues. I do report them, but I think technical issues are by far more interesting.)
(In reply to André Bargull from comment #3)
> (In reply to Rick Waldron from comment #1)
> > > Step 2: Remove colon
> > > Step 2.a.i: Omit "then"
> >
> > These are remnants of 1st Edition. Today was the deadline and removing
> > colons and the word "then" in a panic all night is not a good use of
> > anyone's time.
>
> Sure, I understand that. That's just minor nit-picking to align the style
> with ES2015, but it's totally up to you if you want to mimic Allen's style
> from ES2015. You're the editor of the ECMA-402 spec, so I'm also ok if you
> prefer a different style or if you say you don't care about these things.
> (TBH, actually I don't even care about most editorial issues. I do report
> them, but I think technical issues are by far more interesting.)
I ended up making every single change that you reported ;)