Open JCKodel opened 1 year ago
Thanks for filing an issue! This is a duplicate of https://github.com/dart-lang/sdk/issues/45372
@JCKodel, I suggested a way to conceptualize the behavior of 'strict-raw-types' on https://github.com/dart-lang/sdk/issues/45372: One way to see it is that we're flagging types that contain dynamic
implicitly, another way to see it is that we're flagging raw types in general. The actual behavior is to flag the former, not the latter.
However, in this case I think the relevant setting is 'strict-inference', not 'strict-raw-types' (there are no raw types in the example).
@srawlins, if this is true then maybe this isn't a duplicate of https://github.com/dart-lang/sdk/issues/45372 after all? I suppose the behavior of 'strict-raw-types' and the behavior of 'strict-inference' are two different topics?
Good catch
Describe the issue
While using this analysis_options.yaml:
This example only triggers a warning in the first usage (while it should trigger for both):