On Tue, Jul 3, 2012 at 1:01 AM, Robert Marianski wrote:
> I can confirm that this patch resolves the issue for me. Thanks!
>
> As to whether null and undefined should be interchangeable, I'm not sure
> what the right answer is. I think that depends on how many times
> undefined is returned as a re
I can confirm that this patch resolves the issue for me. Thanks!
As to whether null and undefined should be interchangeable, I'm not sure
what the right answer is. I think that depends on how many times
undefined is returned as a result from a cljs function. If it happens
pretty often, then we pro
The problem is partly with (hash js/undefined) and partly with (:foo
{}) -- the former is broken on master, the latter returned
js/undefined.
Ticket is here with a fix for the first problem is here:
http://dev.clojure.org/jira/browse/CLJS-330
The ticket description mentions further issues. In pa
I see where the problem is and I've got a possible fix. I'll go ahead
and open a ticket; I'll be right back with a link.
Cheers,
Michał
On 3 July 2012 04:40, David Nolen wrote:
> Please open a ticket with these details:
> http://dev.clojure.org/jira/browse/CLJS
>
> Thanks!
>
> David
>
> On Mon
Please open a ticket with these details: http://dev.clojure.org/jira/browse/CLJS
Thanks!
David
On Mon, Jul 2, 2012 at 10:37 PM, Robert Marianski wrote:
> I'm getting an error when trying to call a multimethod in a certain
> scenario. I'm unfortunately not able to reproduce this when running it
I'm getting an error when trying to call a multimethod in a certain
scenario. I'm unfortunately not able to reproduce this when running it
as a test case with v8. But, I was able to trim it down to the following
test case which fails for me in a browser (with a connected repl).
(defmulti foo (fn
