Konstantin Scheglov
Konstantin Scheglov
> > I don't know. To answer this I need to understand better if we need two separate sets of libraries / packages to write macros, and to compile macro...
@fshcheglov This is related to https://github.com/dart-lang/sdk/issues/56559, you should be able to solve it.
Yes, I think we probably will not able to switch completely until `analyzer 8.0.0` is published.
Yes, maybe Dart SDK is not there, or in process of being updated, so incomplete.
This is the same exception again, I still suspect that this is because we try to do more than one operation concurrently in DAS: analysis and handling requests. The solution...
> @josephemorgan I wouldn't expect nested projects or path dependencies to cause any additional problems. Changing code in one project may result in code in the other project being re-analyzed,...
I'm not sure if this can work. Theoretically, the macro code generator cannot invoke `resolveIdentifier` during the types phase. We don't have all types yet, so we cannot resolve them....
Interesting. You are probably right that theoretically we know `MacroExecutionResult.newTypeNames` from all macro applications in all libraries of the library cycle, and so we could know the location of each...
Probably not very useful. First of all, I don't see wildcard variables used widely, but correct me if I'm wrong. Then, which wildcard "variables" do we want to highlight differently?...
@fshcheglov I think this is a good issue for you to solve.