mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
730d6d44b7
Full context https://github.com/flutter/flutter/issues/148004 TL;DR 1. Because `package:macros` depends on `package:_macros` via [a Dart SDK dependency](https://github.com/dart-lang/sdk/blob/main/pkg/macros/pubspec.yaml#L13); and 2. `package:macros` exactly pins `package:_macros`; and 3. Each new version of `package:macros` will increment its exact pin of `package:_macros` ([comment](https://github.com/flutter/flutter/issues/148004#issuecomment-2103099893)); and 4. The [flutter/flutter](https://github.com/flutter/flutter) repository exactly pins the Dart SDK (via its exact pin on the [flutter/engine](https://github.com/flutter/engine) repository Therefore, the [flutter/flutter](https://github.com/flutter/flutter) repository effectively pins both `package:macros` and `package:_macros` already (as in, there exists only a single version of each that pub will successfully be able to solve within the context of a particular Flutter SDK). Therefore, it is safe for [flutter/flutter](https://github.com/flutter/flutter) repository to *not* pin `package:macros`, which will allow engine -> framework rolls that contain a new Dart SDK that contains a new `package:_macros` version to land automatically, provided all tests pass. |
||
|---|---|---|
| .. | ||
| android | ||
| ios | ||
| lib | ||
| macos | ||
| test | ||
| test_driver | ||
| test_memory | ||
| windows | ||
| pubspec.yaml | ||
| README.md | ||
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.