commit | e2cd8be814d91cbe3ade42933d506508538858e9 | [log] [tgz] |
---|---|---|
author | Jake Macdonald <jakemac@google.com> | Tue Jun 01 19:29:54 2021 +0000 |
committer | commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jun 01 19:29:54 2021 +0000 |
tree | 8bce06e0b2cd95aae2b5cd45f3bb9a78e7d50a55 | |
parent | 8580370162ad5f0cb801de383104fccf6b47cf42 [diff] |
Revert "Move most of the code from u/b/kernel_worker.dart to p/frontend_server" This reverts commit 659fdae898d4c1095bfb9c76617f3c34686a82a7. Reason for revert: Broke the HHH bots. The fix according to zra@ should be: "The new dependencies should be added as dependency overrides to flutter_frontend_server's pubspec.yaml: https://github.com/flutter/engine/blob/master/flutter_frontend_server/pubspec.yaml" Original change's description: > Move most of the code from u/b/kernel_worker.dart to p/frontend_server > > This should allow us to import the code in cases when we want to > implement the Bazel worker loop ourselves. This opens some possibilities > of extra optimizations for internal use cases. > > I'm leaving some of the code (e.g., `main`) in the old location, so that > we do not break anything that depends on it. > > The only thing that I've done is to pass the input-digest map to > `computeKernel` instead of using `Input` objects directly, this way > we can avoid the dependency on `package:bazel_worker` from > `frontend_server`. So now, if we're using the worker loop, the map will > be computed by `kernel_worker.dart` (in non-worker mode, we rely on > the default empty map). > > Bug: http://b/187910394 > Change-Id: I408407ebdebc17c7898552c053a8e1c269cf2df5 > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/201187 > Commit-Queue: Michal Terepeta <michalt@google.com> > Reviewed-by: Johnni Winther <johnniwinther@google.com> # Not skipping CQ checks because original CL landed > 1 day ago. Bug: http://b/187910394 Change-Id: Ieb44d61b668a7d4629a27eef5a6ef61d0db9deaf Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/201880 Reviewed-by: Jake Macdonald <jakemac@google.com> Reviewed-by: Alexander Aprelev <aam@google.com> Reviewed-by: Phil Quitslund <pquitslund@google.com> Auto-Submit: Jake Macdonald <jakemac@google.com> Commit-Queue: Jake Macdonald <jakemac@google.com> Commit-Queue: Alexander Aprelev <aam@google.com> Commit-Queue: Phil Quitslund <pquitslund@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.