Sam Rawlins
Sam Rawlins
(this is more a bug on the existing rule than a proposal for a new rule) I think this would be a good improvement, and would keep in line with...
The rule is not in place to encourage shorter code, but to encourage more performant code (I think) which doesn't involve unnecessary closures. In any case it's more idiomatic (https://dart.dev/guides/language/effective-dart/usage#avoid-using-iterableforeach-with-a-function-literal)....
@Erhannis thanks for filing an issue. > I see lint rules like https://dart-lang.github.io/linter/lints/discarded_futures.html with "Maturity: stable", but are not present in the stable release. The linter package doesn't have stable...
> It still seems excessively difficult to figure out whether you can use a given lint rule or not. That's fair. I think it is a separate issue from how...
This is resolved.
Foo and BarBase are unrelated classes. Why should a lint not be reported?
> how is `Foo` any more related to a `T` that extends the same abstract class `BarBase`? `==` with a `T` is treated differently because `T` is not a type,...
And `Queue.from` => `Queue.of`.
@Levi-Lesches to answer [your question](https://github.com/dart-lang/linter/issues/2555#issuecomment-878701272), which holds with @rakudrama 's initial suggestion, is that we would _not_ report a `List.from` if the explicit type argument `E` in `List.from(iterable)` is _not_...
@bwilkerson any updates here? I'm not sure the premise is correct... I think `var foo;` is `dynamic`, even if it is definitely assigned later.