History

[flutter_tools] update to vm_service 5.2.0, update to dwds 7.0.0 (#69067 )

Rolls in several fixes to web tooling, including better handling of absolute file imports. Updates to latest vm service to unblock null safety mode query

Co-authored-by: Gary Roumanis <grouma@google.com>
Co-authored-by: Anna Gringauze <annagrin@google.com>

2020-10-27 13:55:32 -07:00

android

move compile/target sdk versions to 29 (#62799 ) (#63008 )

2020-08-11 14:51:02 -07:00

ios

Revert "Build iOS apps using Swift Packages (#68361 )" (#68546 )

2020-10-19 17:57:32 -07:00

lib

use_is_even_rather_than_modulo (#68301 )

2020-10-16 20:20:00 +02:00

pubspec.yaml

[flutter_tools] update to vm_service 5.2.0, update to dwds 7.0.0 (#69067 )

2020-10-27 13:55:32 -07:00

README.md

Restore the original name of the velocity tracker microbenchmark (#64060 )

2020-08-19 00:41:06 -07:00

README.md

microbenchmarks

To run these benchmarks on a device, first run `flutter logs' in one window to see the device logs, then, in a different window, run any of these:

flutter run --release lib/gestures/velocity_tracker_bench.dart
flutter run --release lib/gestures/gesture_detector_bench.dart
flutter run --release lib/stocks/animation_bench.dart
flutter run --release lib/stocks/build_bench.dart
flutter run --release lib/stocks/layout_bench.dart

The results should be in the device logs.

Avoid changing names of the benchmarks

Each microbenchmark is identified by a name, for example, "catmullrom_transform_iteration". Changing the name of an existing microbenchmarks will effectively remove the old benchmark and create a new one, losing the historical data associated with the old benchmark in the process.