Analyzer: Fix incorrect type in PropertyElementResolver._resolve. The `unpromotedType` computed by `PropertyElementResolver._resolve` (which eventually propagates to both `FlowAnalysis.propertyGet` and to `PropertyElementResolverResult.getType`) is intended to represent the static type of the "property get" expression in the absence of promotion. If the property get targets a `PropertyAccessorElement` (a getter), this is the getter's return type. But if it targets a `MethodElement`, this is the function type of the method (because the "property get" is doing a tear-off of the method). Previously, `PropertyElementResolver._resolve` was always using the return type, meaning that if the property get was targeting a `MethodElement`, it was computing the wrong type. Fortunately, this didn't lead to any bugs, because (a) the type passed to `FlowAnalysis.propertyGet` is only used for determining whether a field access should be promoted, and method tear-offs aren't promotable, and (b) the analyzer only uses the type stored in `PropertyElementResolverResult.getType` when the element being targeted is a `PropertyAccessorElement`. I'm in the middle of a larger arc of work trying to introduce a new, simpler mechanism for flow analysis to be told about the static types of property gets, and part of that arc of work will involve introducing a temporary check to verify that the old and new mechanisms see the same static types. Fixing this incorrect type will allow the temporary check to pass. Change-Id: Ib13b12d1176a781dc56c3e79c150df481b48a0d5 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/390585 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> https://dart.googlesource.com/sdk/+/37ae078a3036578f9ae471d536384445a569cdf5
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.