Konstantin Scheglov
Konstantin Scheglov
@fshcheglov I think this is a good issue for you to solve.
Ah, this is a good question about all other annotations. I also think moving all annotations to the getter / setter is right. It is impossible to know the intention...
I suspect that we should use relative URIs. And you have such relative URI. Why don't you use it?
Yes, it is expected right now that after linking, `LibraryElement`s take more memory than they usually do when loading from the cache. The reason is that after linking, a `LibraryElement`...
This works as intended. 1. Users change `analysis_options.yaml` files rarely, so it is not worth investing our time into optimizing it. 2. Identifying fine grained changes in options is hard...
A subtype of `MyBox` will inherit implementation of `==` from `Object`. Although I don't think that the issue is the `==`. The warning looks reasonable to me. I don't know...
This program crashes: ```dart import 'test4.dart'; class MyBox2 implements MyBox { int _value = 0; } void main() { MyBox(0) == MyBox2(); } ``` ```dart class MyBox { final int...
I cannot reproduce this, and AFAIK we have never seen anything like this before. Also, the analyzer package itself has not yet enabled Dart 3.0, so it is probably unrelated...
It seems that we have a state with misconfigured language features for these libraries, that makes the parser to produce mixins with empty names. And then `[` is parsed as...
The type inference issue seems quite different to me. So, please, open a new issue.