commit | fb449ed038c8267c451d1682dbac0d9e1bef9b79 | [log] [tgz] |
---|---|---|
author | Paul Berry <paulberry@google.com> | Fri Jan 12 19:31:40 2024 +0000 |
committer | dart-internal-monorepo <dart-internal-monorepo@dart-ci-internal.iam.gserviceaccount.com> | Fri Jan 12 11:36:13 2024 -0800 |
tree | e1374ea2157be51d5f81a0f57f4b0527eb8d5f91 | |
parent | 82b05be1120a1ede25988a63ba1c37cbe667ec5b [diff] |
Fix handling of extension types in relational patterns. In https://dart-review.googlesource.com/c/sdk/+/345082, type erasure was added to the handling of relational patterns, to address some co19 failures, e.g.: extension type const BoolET1(bool _) {} const True1 = BoolET1(true); String testStatement1(bool b) { switch (b) { case == True1: ... } } This was failing because the type of `True1` (`BoolET1`) is not assignable to the argument type of `operator==`, which is `Object`. (This is because extension types do not, by default, extend `Object`; they extend `Object?`). Adding type erasure elimited the co19 failure, but it caused other code to be allowed that shouldn't be allowed, such as: extension type const E(int representation) implements Object {} class A { bool operator <(int other) => ...; } const E0 = E(0); test(A a) { if (a case < E0) ...; } This shouldn't be allowed because the type expected by `A.<` is `int`; allowing `E0` to be passed to this operator breaks extension type encapsulation. The correct fix is for assignability checks for `operator==` to use `S?` rather than `S`, where `S` is the argument type of `operator==`. This is consistent with the patterns specification, and it ensures that `== null` and `!= null` are allowed, while continuing to prohibit relational patterns that break extension type encapsulation. Fixes https://github.com/dart-lang/sdk/issues/54594. Bug: https://github.com/dart-lang/sdk/issues/54594. Change-Id: Id090f432500d75ba694383f1788d58353cd1fc72 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/345860 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Paul Berry <paulberry@google.com> https://dart.googlesource.com/sdk/+/973eca72f559493ee504bf694845d1389546ec39
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.