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
There is only one path receiver that uses this method and it is only ever used from within the utility helper methods within one class (PathTessellator). In all other classes it is ignored because they don't care about knowing when the path is done. Additionally there are cases where multiple PathSource objects are used together to compose a longer path and so while each might think the "path is done" (i.e. send PathEnd()), they would not be correct in those cases.
Rather than make this the responsibility of all PathSource objects to send this final method call, which is ignored in most cases, we should just have the one case where "final processing" is a necessary requirement define that the process of feeding that one object includes letting it know when all of the path segments are done.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
[Impeller] eliminate PathReceiver::PathEnd which is only used in one …
[Impeller] eliminate PathReceiver::PathEnd which is only used in one …
github-actions commentedon Jun 28, 2025
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.[Impeller] eliminate PathReceiver::PathEnd which is only used in one …
[Impeller] eliminate PathReceiver::PathEnd which is only used in one …