my opinion:
I think this feature is not good because fundamentally, I don't think the following constructs should behave differently at type time because they behave the same at runtime:
a: object = 1
b: object
b = 1
I think the argument for it, is that an assignment has an explicit type annotation, so that 'should' be used for the type.
my opinion: I think this feature is not good because fundamentally, I don't think the following constructs should behave differently at type time because they behave the same at runtime:
I think the argument for it, is that an assignment has an explicit type annotation, so that 'should' be used for the type.