You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to port macro arguments to the new macro system, starting with the easier constants (so no Code or TypeAnnotation initially).
It would help to have an idea on how to pass this information to macro implementation. I was thinking about having a representation for constants similar to the DartObject class from the analyzer (so a fully resolved constant instead of a syntax-related representation of the macro annotation).
The question is how we'd pass this to the macro implementation. Considering an argument like this:
I would like to port macro arguments to the new macro system, starting with the easier constants (so no
Code
orTypeAnnotation
initially).It would help to have an idea on how to pass this information to macro implementation. I was thinking about having a representation for constants similar to the
DartObject
class from the analyzer (so a fully resolved constant instead of a syntax-related representation of the macro annotation).The question is how we'd pass this to the macro implementation. Considering an argument like this:
Perhaps we could pass the information about the instantiated macro along as part of the
Model
? Or we could add a getter toBuilder
, like thisWhich the implementation could then query like this:
I'm happy to wire up the implementation myself, but some guidance on how the API should look like would be helpful :)
The text was updated successfully, but these errors were encountered: