| commit | a32faf43fcc89a84eafdb19ae00d3aa32a39cd92 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Thu Jun 19 11:13:27 2025 -0700 |
| committer | dart-internal-monorepo <dart-internal-monorepo@dart-ci-internal.iam.gserviceaccount.com> | Thu Jun 19 11:15:42 2025 -0700 |
| tree | 66119a08bb089f471a4063220b8e4e36fab28201 | |
| parent | 567e6839a255a29a6c938e605302369b4ae0d282 [diff] |
[analyzer] Simplify and clean up duplicate declaration checking. This change reworks `MemberDuplicateDefinitionVerifier._checkConflictingConstructorAndStatic` and `MemberDuplicateDefinitionVerifier._checkDuplicateIdentifier` into a form that is easier to reason about and has slightly faster performance (measured by instruction count). In the previous design, two maps were maintained for each scope in which getters and setters might appear: - one called `getterScope`, which (confusingly) held getters, setters, and method declarations, - and one called `setterScope` which only held setters. This was difficult to reason about. In particular, it had a longstanding bug that was only recently fixed (see https://dart-review.googlesource.com/c/sdk/+/434061): if a setter was encountered first, it was stored in `getterScope`, but if a getter was encountered next, it was necessary to move the setter to `setterScope` in order to store the getter in `getterScope`. It was also inefficient, since in many cases, two map lookups were needed in order to check for both getter and setter conflicts. In the new design, there is a single map, whose values point to either a `_ScopeEntryFragment` (in the case where just one declaration of the given name has been seen) or a `_ScopeEntryGetterSetterPair` (in the case where both a getter and a setter have been seen). The new design has modestly better performance when measured by front_end/tool/benchmarker.dart: Comparing snapshot #1 (before.aot) with snapshot #2 (after.aot) instructions:u: -0.0192% +/- 0.0131% (-6291379.67 +/- 4292101.91) (32692292436.33 -> 32686001056.67) Change-Id: Ia6675fa4d3579779e6066db3760d2cc38a2c859e Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/435602 Reviewed-by: Jens Johansen <jensj@google.com> Commit-Queue: Paul Berry <paulberry@google.com> https://dart.googlesource.com/sdk/+/5fc5f3678ac03b28ea462101eab76305caee0eb4
Monorepo is:
With depot_tools installed and on your path, create a directory for your monorepo checkout and run these commands to create a gclient solution in that directory:
mkdir monorepo cd monorepo gclient config --unmanaged https://dart.googlesource.com/monorepo gclient sync -D
This gives you a checkout in the monorepo directory that contains:
monorepo/ DEPS - the DEPS used for this gclient checkout commits.json - the pinned commits for Dart, flutter/engine, and flutter/flutter tools/ - scripts used to create monorepo DEPS engine/src/ - the flutter/buildroot repo flutter/ - the flutter/engine repo out/ - the build directory, where Flutter engine builds are created third_party/ - Flutter dependencies checked out by DEPS dart/ - the Dart SDK checkout. third_party - Dart dependencies, also used by Flutter flutter/ - the flutter/flutter repo
Flutter's instructions for building the engine are at Compiling the engine
They can be followed closely, with a few changes:
goma_ctl ensure_start is sufficient.Example build commands that work on linux:
MONOREPO_PATH=$PWD if [[ ! $PATH =~ (^|:)$MONOREPO_PATH/flutter/bin(:|$) ]]; then PATH=$MONOREPO_PATH/flutter/bin:$PATH fi export GOMA_DIR=$(dirname $(command -v gclient))/.cipd_bin goma_ctl ensure_start pushd engine/src flutter/tools/gn --goma --no-prebuilt-dart-sdk --unoptimized --full-dart-sdk autoninja -C out/host_debug_unopt popd
The Flutter commands used to build and run apps will use the locally built Flutter engine and Dart SDK, instead of the one downloaded by the Flutter tool, if the --local-engine option is provided.
For example, to build and run the Flutter spinning square sample on the web platform,
MONOREPO_PATH=$PWD cd flutter/examples/layers flutter --local-engine=host_debug_unopt \ -d chrome run widgets/spinning_square.dart cd $MONOREPO_PATH
To build for desktop, specify the desktop platform device in flutter run as -d macos or -d linux or -d windows. You may also need to run the command
flutter create --platforms=windows,macos,linux
on existing apps, such as sample apps. New apps created with flutter create already include these support files. Details of desktop support are at Desktop Support for Flutter
Tests in the Flutter source tree can be run with the flutter test command, run in the directory of a package containing tests. For example:
MONOREPO_PATH=$PWD cd flutter/packages/flutter flutter test --local-engine=host_debug_unopt cd $MONOREPO_PATH
Please file an issue or email the dart-engprod team with any problems with or questions about using monorepo.
We will update this documentation to address them.
flutter commands may download the engine and Dart SDK files for the configured channel, even though they will be using the local engine and its SDK.gclient sync needs to be run in an administrator session, because some installed dependencies create symlinks.