http://d.puremagic.com/issues/show_bug.cgi?id=9514
--- Comment #3 from David Nadlinger <c...@klickverbot.at> 2013-02-15 12:14:19 PST --- (In reply to comment #2) > Let's back to the Thrift code issue. This is just my prediction, the Foo > declaration contains "mixin TStructHelpers!(...)", and it may have some > forward > reference error as like explained above. Okay, the issue seems to be connected to the fact that the code contains an import cycle between thrift.internal.codegen and thrift.codegen.base (that I probably introduced by accident while refactoring). You say that you think that this is not a compiler issue. Could you elaborate a bit? Moving the struct inside the unittest block hides the problem because the struct is no longer semantic'd. But I'm not sure what part of the code would be illegal in the first place? I can certainly work around the issue in the Thrift tests (although it's a bit cumbersome, as I don't have commit access). The thing I'm worried about is pushing out a release with a known regression/change in behavior that leads to a completely nonsensical error message and might also occur in other code. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
