commit 3f93da5fdaf03ea14d073b9ce629fe31dc17a0b8
author scottb@google.com <scottb@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Fri Aug 14 21:43:27 2009 +0000
committer scottb@google.com <scottb@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Fri Aug 14 21:43:27 2009 +0000
tree 9fde99def1c05fb8defd02c56c18c6b532e24273
parent 171dd1614fb0c8abcd36c8012cc198dcb6886571

Issue 3936: work around JDT by not computing CUD from scope chain.

It appears JDT has a bug where it will pass you a null scope while visiting the expression of an empty switch statement. See:

http://code.google.com/p/google-web-toolkit/issues/detail?id=3936

It turns out, however, that TypeRefVisitor was only using the scope chain to compute the containing CUD on the fly.  Since this visitor always traverses entire CUDs, we can work around the JDT scope issue by just requiring the CUD to be set up front.

Review by: spoon

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