On Wed, Jun 8, 2011 at 8:40 PM, <[email protected]> wrote: > General question: I'm curious why this couldn't be simpler, that is, why > does unification depend on control flow? Couldn't you unify everything > without respect to control flow, and then run a pruning pass afterwards > reusing the existing CFA code, or is doing it in an integrated pass an > attempt to scope down the amount of work done?
I think that could be one good reason; In some cases, there can be thousands of unreferenced types in a project. stitching those units would be a waste of time and memory. Also, since we often encounter projects that include untranslatable code on the source path, the JDT compile step and build Type Oracle step doesn't show the errors (unless you turn on strict mode). We rely on the AST building stage to report the "important" errors. -- Eric Z. Ayers Google Web Toolkit, Atlanta, GA USA -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
