[dart2wasm] Implement micro-task scheduling Use JS `setTimeout` for events and `queueMicrotask` for micro-tasks. dart2js event loop implementation is copied in `run_wasm.js` to be able to use `clearTimeout`, `setInterval`, `clearInterval`, and `scheduleMicrotask`, which are not not available in d8, and `setTimeout` in d8 does not wait before calling a callback. New passing d8 tests: - co19/LibTest/async/Future/Future.delayed_A01_t02 - co19/LibTest/async/Stream/Stream.periodic_A01_t01 - co19/LibTest/async/Stream/Stream.periodic_all_t01 - co19/LibTest/async/Stream/Stream.periodic_all_t02 - co19/LibTest/async/Stream/timeout_A04_t01 - co19/LibTest/async/StreamController/stream_all_A01_t01 - co19/LibTest/async/StreamController/stream_all_A01_t02 - co19/LibTest/async/StreamController/stream_all_A02_t01 - co19/LibTest/async/StreamController/stream_all_A02_t02 - co19/LibTest/async/StreamController/StreamController.broadcast_Stream_all_A01_t01 - co19/LibTest/async/StreamController/StreamController.broadcast_Stream_all_A01_t02 - co19/LibTest/async/StreamController/StreamController.broadcast_Stream_all_A02_t01 - co19/LibTest/async/StreamController/StreamController.broadcast_Stream_all_A02_t02 - co19/LibTest/async/Timer/Timer.periodic_A01_t01 - co19/LibTest/async/Timer/Timer_A01_t01 - co19/LibTest/core/Stopwatch/elapsedTicks_A01_t01 - language/async/call_test - language/regress/regress21795_test - lib/async/multiple_timer_test - lib/async/periodic_timer2_test - lib/async/periodic_timer3_test - lib/async/periodic_timer4_test - lib/async/schedule_microtask3_test - lib/async/schedule_microtask_test - lib/async/stream_timeout_test - lib/async/timer_isActive_test - lib/async/timer_repeat_test - lib/async/timer_test New passing Chrome tests: - co19/LibTest/async/Stream/timeout_A04_t01 - language/async/call_test - lib/async/schedule_microtask3_test Tests below fail because of async* desugaring issues and will be fixed separately: - language/async_star/no_cancel2_test - language/async_star/no_cancel_test Tests below fail because of an existing issue (#29615): - co19/LibTest/async/StreamController/StreamController.broadcast_Stream_all_A01_t03 - co19/LibTest/async/StreamController/StreamController.broadcast_Stream_all_A02_t03 - co19/LibTest/async/StreamController/stream_all_A02_t03 Fixes #51599. Change-Id: Ib313e99bf3b3cb3bebeddc9e47dc77425ef94481 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/305201 Reviewed-by: Aske Simon Christensen <askesc@google.com> Reviewed-by: Joshua Litt <joshualitt@google.com> Commit-Queue: Ömer Ağacan <omersa@google.com> https://dart.googlesource.com/sdk/+/87a3de41b10d292d3069b2cca0cae13837669099
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.