commit | dbd9f2d59b393a3244308506e6e233d5d584be95 | [log] [tgz] |
---|---|---|
author | Kallen Tu <kallentu@google.com> | Tue Oct 15 19:12:31 2024 +0000 |
committer | dart-internal-monorepo <dart-internal-monorepo@dart-ci-internal.iam.gserviceaccount.com> | Tue Oct 15 12:17:02 2024 -0700 |
tree | 5e140baff2b51618642b7fe4237ec2df5cc56b6b | |
parent | b29a352a46d0d4ad5b6550bceaae08f2c88f5fa6 [diff] |
Enable 'wildcard-variables' feature flag. This CL enables the wildcard variables feature by default in Dart 3.7. Local variables and parameters named `_` are now non-binding and they can be declared multiple times without collisions. All wildcard variable declaration types that have this behavior are described in the wildcard variables specification: https://github.com/dart-lang/language/blob/main/accepted/future-releases/wildcard-variables/feature-specification.md. Top-level variables, top-level function names, type names, member names, etc. are unchanged. They can be named `_` and used as they are today. These are a few examples of where wildcard variables can be used: ```dart Foo(_, this._, super._, void _()) {} typedef T = void Function(String _, String _); main() { var _ = 1; int _ = 2; list.where((_) => true); } ``` Bug: https://github.com/dart-lang/sdk/issues/55673 Fixes: https://github.com/dart-lang/sdk/issues/55654 Change-Id: I80e904d39b364f5e54b8406b4db02ec40ecc9db0 TEST=Existing tests, language tests for wildcards. Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/381311 Reviewed-by: Mark Zhou <markzipan@google.com> Reviewed-by: Mayank Patke <fishythefish@google.com> Reviewed-by: Ben Konyi <bkonyi@google.com> Reviewed-by: Johnni Winther <johnniwinther@google.com> Reviewed-by: Siva Annamalai <asiva@google.com> Commit-Queue: Kallen Tu <kallentu@google.com> Reviewed-by: Phil Quitslund <pquitslund@google.com> Reviewed-by: Bob Nystrom <rnystrom@google.com> https://dart.googlesource.com/sdk/+/1bf5482e1e35ba1b0ccee299887812e6410aa026
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.