Bug fix: order of attribution of lazy constant values
wdietl at gmail.com
Mon Jan 28 00:00:32 PST 2013
in a case study we uncovered a problem with the order of how type
annotations are attributed.
I pushed a test case and simple fix:
Note that the code in
which analyzes a variable initializer, is not executed for a lazy
Is there a nicer place to unify these two separate calls of
Could you file a bug and push this fix to TL?
More information about the type-annotations-dev