Well, I spend time looking into this. Do you have a slightly more "realistic" example? The reason I ask is because there is some logic that tries to eliminate circular dependencies and I can't tell if there is a bug in it or not because in the small test case you provided, the class B is never actually instantiated by any other code.
It might be that we need to not goog.require(B) from A if we can tell that A never instantiated B, but I would rather not have the compiler spend time trying to figure that out. Thanks, -Alex On 11/29/15, 11:22 PM, "Alex Harui" <aha...@adobe.com> wrote: > > >On 11/29/15, 6:38 PM, "lizhi" <s...@qq.com> wrote: > >>test.zip >><http://apache-flex-development.2333347.n4.nabble.com/file/n50345/test.zi >>p >>> >> >>have this error,the release not work. >> >>i do not know,is it can resolve? > >We can try to allow that. The Google folks think you shouldn't have that >kind of circular dependency, though. They would rather you use interfaces >or something like that. > >-Alex >
