
This egotistical PR aims to draw attention to a [style guideline](https://github.com/flutter/flutter/blob/master/docs/contributing/Style-guide-for-Flutter-repo.md#use--for-getters-and-callbacks-that-just-return-literals-or-switch-expressions) that I changed: > #### Use `=>` for getters and callbacks that just return literals or switch expressions <br> There was an opportunity for valuable discussion in #154753 about how this structure affects readability, but I shut it down pretty quick since there was a lot of other stuff going on there. Interested to hear thoughts from @Piinks and others.
complex_layout
Scrolling benchmark
To run the scrolling benchmark on a device:
flutter drive --profile test_driver/scroll_perf.dart
Results should be in the file build/complex_layout_scroll_perf.timeline_summary.json
.
More detailed logs should be in build/complex_layout_scroll_perf.timeline.json
.
Startup benchmark
To measure startup time on a device:
flutter run --profile --trace-startup
The results should be in the logs.
Additional results should be in the file build/start_up_info.json
.