-
Notifications
You must be signed in to change notification settings - Fork 64
Defining and calling mixins from separate files causes "Compiler internal error" #70
Comments
I confirmed this with:
I've looked through that change. The only thing that jumped out at me was the addition of the I'm going to add a test and fix for this internally, then push it back out. Thanks for your excellent bug report! |
BTW, there are actually two errors wrapped up in the same bug.
I've got a fix for (1) that will allow |
Thanks for the prompt reply. Even just fixing (1) allowDefPropagation by default [or with a flag] is good enough for me. The error reporting is far less important from my perspective. |
During a previous refactoring, allowDefPropagation got moved to JobDescription but the ClosureCommandLineCompiler was not updated to set it or provide a default. This fixes issue #70 on GitHub. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=107058094
This should be fixed. |
Thanks! I can confirm that your change resolves my issue. |
When defining and calling a mixin in separate source files the compiler currently (both 1.0 and HEAD) result in a "Compiler internal error". However, this did not used to be the case. A compiler that I build on Dec 23 2014 compiles these inputs just fine.
The text was updated successfully, but these errors were encountered: