Think and discuss two PRs related to NotifyIdle

[fzyzcjy]

flutter/engine#36797

We don't want to expose this kind of internal of the VM to users.
Perhaps it would be more appropriate to expose a different API around whether an animation is occurring currently, although I think @iskakaushik has already done some work on that.

flutter/engine#36834

Same problems as the other NotifyIdle PR - these are details we don't want to expose to users. NotifyIdle might not do anything, or it might do a lot more than the user expects. In all honesty, it would be nice to get rid of it entirely since it is hard to reason about and seems to come out wrong very frequently. If users can change this arbitrarily it will make it much harder to reason about what's going on in an application.
Closing this to remove from review queues. There is definitely work to do around NotifyIdle, but I think we'll need some cooperation from the dart VM team on it.

[fzyzcjy]

replied on github. maybe later discuss on discord or ping?

[fzyzcjy]

(leave this issue open, so not forget I am waiting for reply)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[fzyzcjy]

bump