| commit | 53783889da4c4cd42893dd4d55bc12a65805fd7a | [log] [tgz] |
|---|---|---|
| author | Konstantin Shcheglov <scheglov@google.com> | Mon Aug 25 13:07:02 2025 -0700 |
| committer | dart-internal-monorepo <dart-internal-monorepo@dart-ci-internal.iam.gserviceaccount.com> | Mon Aug 25 13:08:11 2025 -0700 |
| tree | 75658be99e2a853cffe5c5157e0ab40cc888201e | |
| parent | ee06891391cfad85cef6dec6d868f4b23a34e165 [diff] |
Fine. Avoid opaque API uses when lazily loading class members. Lazy loading of a class’s members inadvertently recorded opaque API uses via `ClassElementImpl.fragments`/`firstFragment`. This polluted result requirements with non-API dependencies and could trigger unnecessary rebuilds when reading from cached bundles. This change removes those spurious dependencies: - Add `ClassElementImpl._fragments` to iterate fragments without touching the tracked `fragments` getter. - Add `ClassElementImpl.ensureReadMembersForFragments()` and use it in `BundleReader` when materializing a class’s members, avoiding any dependency on `fragments` during deserialization. - Simplify `LinkedElementFactory` by calling `parentElement.ensureReadMembers()` instead of poking constructor lists to force member loading. - Keep the public `fragments` getter behavior (including opaque tracking) for true API reads; internal reads now use the private helper. A regression test exercises a scenario where class `B` references `A` in a default parameter. Linking after a cache reload no longer records opaque uses of `A`/`B` members, preserving dependency precision. Found with https://dart-review.googlesource.com/c/sdk/+/446480 Change-Id: Ib8d2bea359956d1a24b1117bcb6840dfb3a68253 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/446561 Reviewed-by: Paul Berry <paulberry@google.com> Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@google.com> https://dart.googlesource.com/sdk/+/2fcfdd71ad83113fc9a6058c2a4b77c2278a3045
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.