Jacob MacDonald

For instance today two FunctionDefintionMacros that each call `wrapBody` will result in two different versions of the function being generated.

When running a macro you may want to apply a macro from a later phase to an existing declaration.

Because the build runs on the VM, you can't import flutter, so you can't check if things are subtypes of known flutter types. A possibly solution could be a VM...

Allow a class/mixin to implicitly apply a macro wherever it is mixed in or extended?

2

I am not sure this is a good idea, but filing it to have a central area for discussion. The general idea is to have a mechanism available whereby mixing...

You should be able to run macros on extensions, for instance this would allow you to generate `toJson` extension methods for classes you don't control.

Access to full AST for the immediate declaration

16

At least in the `definition` phase we should consider exposing a `Code` object (or similar) for the immediately annotated declaration. For a class this could include all the members of...

Allow adding metadata to declarations

1

Today you cannot add additional metadata (or macros) to existing declarations, but we may want to allow you to do so. You can add both of these when creating new...

Provide access to metadata

6

The current introspection api does not provide access to metadata annotations on declarations today. You can configure macros themselves by passing info to the constructor, but you can't see any...

Some basic level of support was added, see https://github.com/jakemac53/macro_prototype/pull/11#discussion_r659874208, but we probably want something more explicit.

This would be what you get when you introspect on types in the Declaration phase. Today, we give you a `TypeDeclaration` object, but that gets a bit confusing, because `ClassDeclaration`...