Tom Schuster wrote:
I like to disagree. I was quite familiar with the ES spec about a year
ago and this still confused me. Only because this is pre-existing
doesn't make the language very clear.
I agree it's a bit awkward learning to read every Clause 15 method spec
in terms of the Clause 15 i
I like to disagree. I was quite familiar with the ES spec about a year
ago and this still confused me. Only because this is pre-existing
doesn't make the language very clear.
Tom
On Sun, Mar 17, 2013 at 8:11 PM, Rick Waldron wrote:
>
>
>
> On Sat, Mar 16, 2013 at 7:56 PM, Allen Wirfs-Brock
> wr
On Sat, Mar 16, 2013 at 7:56 PM, Allen Wirfs-Brock wrote:
>
> On Mar 16, 2013, at 4:42 PM, Tom Schuster wrote:
>
> > I would argue that the disclaimer makes this more confusing. I am
> > aware of the behavior that not passed parameters are undefined. But It
> > sounded like we would never execute
On Mar 16, 2013, at 7:40 PM, Brendan Eich wrote:
>
> Object.is() // true
>
> It has a nice existentialist ring to it!
>
perfect for when you "u" or "r" key is broken
allen
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/l
Allen Wirfs-Brock wrote:
On Mar 16, 2013, at 5:02 PM, Tom Schuster wrote:
Also note that with the current definition Object.is() should return
true. I am not really a big fan of that ;)
All standard function have a well specified, but perhaps odd, behavior when no
arguments are passed to the
On Mar 16, 2013, at 5:02 PM, Tom Schuster wrote:
> Also note that with the current definition Object.is() should return
> true. I am not really a big fan of that ;)
All standard function have a well specified, but perhaps odd, behavior when no
arguments are passed to them. It's just how JavaSc
On Mar 16, 2013, at 4:49 PM, Axel Rauschmayer wrote:
> Has using more powerful function/method signatures ever been a consideration
> for the spec? For example, type annotations could replace imperative
> coercions.
I am applying ES6 style default value and rest parameter conventions to the
Also note that with the current definition Object.is() should return
true. I am not really a big fan of that ;)
On Sun, Mar 17, 2013 at 12:56 AM, Allen Wirfs-Brock
wrote:
>
> On Mar 16, 2013, at 4:42 PM, Tom Schuster wrote:
>
>> I would argue that the disclaimer makes this more confusing. I am
>>
On Mar 16, 2013, at 4:42 PM, Tom Schuster wrote:
> I would argue that the disclaimer makes this more confusing. I am
> aware of the behavior that not passed parameters are undefined. But It
> sounded like we would never execute step 1. when the parameter count
> doesn't match. And thus leaving th
Has using more powerful function/method signatures ever been a consideration
for the spec? For example, type annotations could replace imperative coercions.
On Mar 17, 2013, at 0:01 , Allen Wirfs-Brock wrote:
> On Mar 16, 2013, at 11:18 AM, Tom Schuster wrote:
>
>> Looking at the the steps fo
I would argue that the disclaimer makes this more confusing. I am
aware of the behavior that not passed parameters are undefined. But It
sounded like we would never execute step 1. when the parameter count
doesn't match. And thus leaving the result of the call not defined.
On Sun, Mar 17, 2013 at
On Mar 16, 2013, at 3:40 PM, David Bruant wrote:
> Le 16/03/2013 19:18, Tom Schuster a écrit :
>> Hey!
>>
>> Looking at the the steps for Object.is the first sentence just says:
>>> "When the is function is called with arguments value1 and value2 the
>>> following steps are taken:"
>> I don't r
On Mar 16, 2013, at 11:18 AM, Tom Schuster wrote:
> Hey!
>
> Looking at the the steps for Object.is the first sentence just says:
>> "When the is function is called with arguments value1 and value2 the
>> following steps are taken:"
> I don't remember other functions being defined like that. It
Le 16/03/2013 19:18, Tom Schuster a écrit :
Hey!
Looking at the the steps for Object.is the first sentence just says:
"When the is function is called with arguments value1 and value2 the following steps
are taken:"
I don't remember other functions being defined like that. It should at
least s
Sorry for the typo in the title :)
On Sat, Mar 16, 2013 at 7:18 PM, Tom Schuster wrote:
> Hey!
>
> Looking at the the steps for Object.is the first sentence just says:
>> "When the is function is called with arguments value1 and value2 the
>> following steps are taken:"
> I don't remember other
Hey!
Looking at the the steps for Object.is the first sentence just says:
> "When the is function is called with arguments value1 and value2 the
> following steps are taken:"
I don't remember other functions being defined like that. It should at
least say something along the lines of
"When called
16 matches
Mail list logo
