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
{{ message }}
Repository navigation
Move away from cached tear-off closures for performance #5154
Megamorphic calls have caught up in speed -- the transformation done for
RenderObject.performLayout is not needed anymore, even slightly
counter-productive in the AOT case: 1% speedup by reverting to a normal
instance call according to my measurements.
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
Hixie commentedon Jan 26, 2017
This would also speed up reassemble substantially since a lot of the work of reassembling is updating these closure pointers.
cc @johnmccutchan
Try moving from closures to direct calls.
Try moving from closures to direct calls. (#7679)
Roll engine to pick updated dart sdk with NSM and hot reload fix.
Roll engine to pick updated dart sdk with NSM and hot reload fix. (#1…
Roll engine to pick updated dart sdk with NSM and hot reload fix. (fl…
github-actions commentedon Sep 5, 2021
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.