How to handle unexpected extra async tasks after macro execution has completed? about sdk

[scheglov]

Distributed use after free issue :-)

I don't know if this is feasible to implement, but theoretically after each invocation to macro, like buildDefinitionForMethod, there should be no scheduled Futures or Timers left. The macro should be completely done with its work. If it is not, cancel these pending operations, and return the error from the macro side to the compiler side. So, such macro will never complete successfully.

[jakemac53]

cc @munificent @johnniwinther @scheglov for comments/ideas

[jakemac53]

and @davidmorgan as well :)

[jakemac53]

In theory, we could keep a counter for the number of callbacks scheduled vs executed, to know if we have any still running.

cc @natebosch do you know if there is any shared code for this?

[natebosch]

do you know if there is any shared code for this?

I don't know of any shared implementations. The NgZone from angular has some awareness of scheduled vs executed but it's not public and doesn't do exactly this.