History

Implementing null-aware operators throughout the repository (#143804 )

This pull request fixes #143803 by taking advantage of Dart's null-aware operators.

And unlike `switch` expressions ([9 PRs](https://github.com/flutter/flutter/pull/143634) and counting), the Flutter codebase is already fantastic when it comes to null-aware coding. After refactoring the entire repo, all the changes involving `?.` and `??` can fit into a single pull request.

2024-02-23 19:02:22 +00:00

android

Reland "Update gradle lockfiles template (#140115 )" (#143081 )

2024-02-08 16:22:15 +00:00

ios

Migrate Xcode projects last version checks to Xcode 15.1 (#140256 )

2024-01-03 23:05:46 +00:00

lib

Implementing null-aware operators throughout the repository (#143804 )

2024-02-23 19:02:22 +00:00

money_asset_manifest.json

Add asset manifest parsing benchmark (#112836 )

2022-10-07 13:39:35 +00:00

pubspec.yaml

Upgrade leak_tracker. (#143236 )

2024-02-09 14:41:22 -08:00

README.md

…

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.