Konstantin Scheglov

It does require changes on the IDE side, because it is suggestion by suggestion decision. For example `a.dart` might define `A` and re-export `C` from `c.dart`. And `b.dart` might define...

I don't think we need such preference. When there is a choice, it is up to the user to make it - DAS does not know whether to choose `package:flutter/material.dart`...

FWIW, here is the result of fuzzy matching score and relevances. It looks that the relevance for `Scaffold` is `525`, while the relevance for `Scaffold()` is `500`, for the identifier...

@pq @bwilkerson

Yes, "Sort Members" has more details, but for the listed declarations it does mostly as described above. I fully agree with semantic ordering of instance variables. By similar logic we...

Why do we want to ignore `Future`s returned from `then`? It is just another `Future` which you might forget to await for its side effects, moreover this will also bypass...

Yes, I thought that there might be more cases when this lint could be reported. But this specific example that I provided is often used in our code base, as...

The compile time error is found during compilation of `declare_count1_macro.dart` to kernel, so it is when CFE, not the analyzer should apply `@DeclareCount0()`. So, I don't think that this is...

FWIW, in [the experiment in the analyzer](https://github.com/dart-lang/sdk/commit/b89c35472f7b5cf41be01111620f92c644cb4c74) I give macros a complete AST node, e.g. `FieldDeclaration` that has its parent set, and so it is possible to access the enclosing...

You might want to enable the `type_literal_in_constant_pattern` lint. And when we know types, the analyzer reports warnings.