Extend type inferencing of dynamic field or property assigned in constructor or initialization method

[monrealis]

It seems that the correct type is inferred only in the simple way where assignment is made at the location of declaration. Maybe it can be improved?

It does not work, for example, when def variable is assigned in Spock's setup().

Related article from 2009: http://contraptionsforprogramming.blogspot.com/2009/11/how-type-inferencing-for-groovy-in.html

[eric-milles]

[eric-milles]

This is testable for assignment in constructor or initializer block. If that looks good, an additional change will be made to support post-construct and other well-known initializer methods (like Spock's setup).

[monrealis]

Thanks. Since there is no 100% guarantee that the value will not be overwritten with the value of another type from anywhere anyway, it would make sense not to worry too much about false inference and to look for the assignment anywhere, not only in the well-known initializer methods. For example, there may be two Spock tests that assign the value in given section with no assignment in setup.

[eric-milles]

Did you have a chance to test what was implemented? This is not one of those 100% enhancements. Only common cases are going to be properly supported. See also #1056 (odd switch case structures will not infer properly).

[eric-milles]