commit 7950679aa8b67f99028bb2cb15224056d45dc55d
author scottb@google.com <scottb@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Wed Apr 27 20:35:10 2011 +0000
committer scottb@google.com <scottb@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Wed Apr 27 20:35:10 2011 +0000
tree f58b6b1b255c066a3b5333f94a5e882c7ebff26e
parent b0e83a4bb2512410b8564e2276098800c84bd486

Fix a class of compiler bugs related to staticImpl.

Ran into this general class of issue... originally I set out to add staticImpl handling logic to a couple more places, such as ImplicitUpcastAnalyzer.  But the more I thought about it, the more it struck me as a real wart, and one that's not giving us much value.  Perhaps even negative value by causing code bloat.  I think it's much simpler to just never inline staticImpls into the calling virtual method.

http://gwt-code-reviews.appspot.com/1428804/


git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@10091 8db76d5a-ed1c-0410-87a9-c151d255dfc7