Hmmmm....I'm not sure we always know at compile time, how an array was created (they can be passed around and cast to different types, etc.).
Did you check out my latest patch set, I came up with a scheme to use negative queryId's to indicate that it's a dual impl interface. It seems to be passing all my new tests, etc. On 2011/06/29 01:44:27, cromwellian wrote:
Looking at Array.setCheck() it seems this was never supported. What we can do is create a Array.setCheckAllowJso() method, and then insert a call to either setCheck or setCheckAllowJso depending on whether or not the array element type is a single JSO impl. setCheckAllowJso would be identical to setCheck except you'd add an " || Cast.isJavaScriptObject()" to the expression.
-Ray
On Tue, Jun 28, 2011 at 6:00 PM, <mailto:jbrosenb...@google.com>
wrote:
> I can verify that my new tests for dualImpls fail going way back, at > least until last August. The other tests all passed, up until
the
> "Overlay overhaul" release this last March. > > http://gwt-code-reviews.appspot.com/1470801/ > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors >
http://gwt-code-reviews.appspot.com/1470801/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
