Konstantin Scheglov
Konstantin Scheglov
A library is usually one file - you can open it and scroll, look on all methods at once, quickly navigate back and forth. Macro generated code should be just...
My long time hypothesis is that this is caused by attempt to run multiple async operations in parallel. Probably here quick fix, file system change event, and the analysis driver....
IIUC, with changes that @pq implemented, there are no such thing as "experiments in a package". There are `analysis_options.yaml` file that govern analysis of some Dart files. I propose that...
A user should rarely enable experiments at all. But if he does, I think it is fine for us to implement it the most straightforward way. Here this means using...
> > We will have to walk to the root only once. > > I don't know what that means. > > If a package under development depends on another...
The way it is supposed to work is that Analysis Server returns completions, and each completion has location - file and offset. When the user selects a completion, IDE requests...
The types/declarations phases are already mostly implemented, I don't see why we should split them into `v2`. I don't agree that separation between the user written library and the generated...
@tatumizer @davidmorgan I don't think that composability is a serious issue. The order of macro applications is well [specified](https://github.com/dart-lang/language/blob/main/working/macros/feature-specification.md#application-order), the user has control which macros are applied after which, and...
@tatumizer Indeed, it will require the developer who adds macro application to understand what these macros do. This is the point where macros are "tested" together. Sometimes you want to...
It looks to me that the clients of the analyzer as a library will not able to analyze Dart code that contains macro applications, because they don't go through "analyzer...