Re: undefined being treated as a missing optional argument

On Apr 13, 2012, at 3:42 PM, Sam Tobin-Hochstadt wrote: On Fri, Apr 13, 2012 at 5:42 PM, Brendan Eich bren...@mozilla.org wrote: Sam has similar testimony from Racket (neé PLT-Scheme). Very much so -- I've encountered places where Racket's semantics for keyword arguments (which is similar

Re: callable objects ?

It would be amazing to have clojure like protocols in JS even without `IFn`. I think it's very good feet and very useful in JS where each library has it's own flavored API. I wrote more about it here: http://jeditoolkit.com/2012/03/21/protocol-based-polymorphism.html#post Also why would

Proxies and observable spec algorithms

Hi, Today, I came across a test on Firefox test suite [1]. This test verifies that on the proxy, the traps gets called in the right order according to the ES5 algorithm of Array.prototype.splice. Seeing this test made me realize that as soon as proxy gets in the spec and implemented in web

Re: callable objects ?

Irakli Gozalishvili wrote: It would be amazing to have clojure like protocols in JS even without `IFn`. I think it's very good feet and very useful in JS where each library has it's own flavored API. I wrote more about it here:

Re: Proxies and observable spec algorithms

It's already the case that the ordering of most [[Put]] and [[Get]] calls in those algotitms are observable. Other internal methods are observable via attribute manipulation side-effects that cause downstream internal methods to throw.  I don't thing Proxies will make things much worse.  That