http://dev.clojure.org/jira This file is an XML representation of an issue en-us 4.4 649 25-07-2011 http://dev.clojure.org/jira/browse/CLJS-439 ClojureScript <p>The default impl uses <tt>(identical? (type x) js/Object)</tt>, but objects created in another JS context (e.g. another frame) will fail this test, since their constructor is a <em>different</em> js/Object. Thus js-&gt;clj is the identity on such objects.</p> <p>I wonder if there are any related problems anywhere else, e.g. with protocols? This seems to be the only occurrence of <tt>js/Object</tt>.</p> <p>Maybe this can be fixed by extending IEncodeClojure to object? I don't immediately see how to do that without incurring the option destructuring overhead recursively.</p> CLJS-439

IEncodeClojure only works on same-context Objects

Defect Minor Resolved Declined Unassigned Tom Jack Tue, 11 Dec 2012 18:54:11 -0600 Sun, 20 Jan 2013 00:52:27 -0600 Sun, 20 Jan 2013 00:52:27 -0600 0 3 <p>I don't think this is something that ClojureScript should try to address at all. To me it seems similar to various classloader issues in JVM land.</p> <p>OK, I don't disagree.</p> <p>This is causing some unpleasantness, and I'm not aware of the classloader issues. Why check (identical? js/object x) instead of (goog.isObject x) on <a href="https://github.com/clojure/clojurescript/blob/master/src/cljs/cljs/core.cljs#L6948">https://github.com/clojure/clojurescript/blob/master/src/cljs/cljs/core.cljs#L6948</a> ? </p> <p>this bit me as well and I can't see a downside to using goog.isObject. I agree with David about not going down a rabbit hole here, but I think we can do the "right thing" for free.</p> <p>EDIT: I spoke too soon. Looks like native objects, like dom nodes would blow up in this scenario. Also, goog.isObject returns true on functions, but that would be easy enough to deal with.</p> <p>I suppose extending to object would similarly cause trouble for dom nodes etc?</p> <p>If you can get ahold of the js/Object from another frame, is it possible to extend IEncodeClojure to it?</p> <p>I have some experience with this stuff - it's a rabbit hole. There are many objects that can cross contexts for which we can provide no sensible equality guarantees. If you need to move data between JS contexts then use GClosure and stick to the basic JS data types. I'm inclined to close this one unless someone has a brilliant comprehensive solution that I'm not seeing right now.</p> <p>This one is tricky. Closing for now.</p> Global Rank