commit | 4919729f00b5c9d2c2962868f4a14815b25f6367 | [log] [tgz] |
---|---|---|
author | Zach Anderson <zra@google.com> | Thu Apr 06 14:43:18 2023 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 06 14:43:18 2023 +0000 |
tree | d236f28ceb35755542b9efaa22b9b246af1389fe | |
parent | df761ba9e7e55dfe867759f7090e26acca529d80 [diff] |
Revert "Reland "[pkg:js/dart:js_interop] Move annotations to dart:_js_annotations"" This reverts commit 9e1997971e6abb3283567adb5480fbb0fb0cb040. Reason for revert: Breaks Dart -> Engine roll? See: https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20linux_web_engine/1821/overview https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20Engine%20Drone/666824/overview Original change's description: > Reland "[pkg:js/dart:js_interop] Move annotations to dart:_js_annotations" > > This is a reland of commit fbe9c2197221a9aca98ae4aaa766164e8ab12d78 > > This fixes the issue with the duplicate allowPlatformPrivateLibraryAccess. > > Original change's description: > > [pkg:js/dart:js_interop] Move annotations to dart:_js_annotations > > > > This moves package:js annotations to the internal library that > > Flutter has been using already. This gives us a single location > > for all package:js annotations. We also introduce a @JS annotation > > in dart:js_interop since we can no longer use dart:_js_annotations > > to avoid the breaking change in semantics. > > > > CoreLibraryReviewExempt: Backend-specific internal library. > > Change-Id: I9ca55c807d7d192004a6da99f63a72d598fe4f12 > > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/284760 > > Commit-Queue: Srujan Gaddam <srujzs@google.com> > > Reviewed-by: Samuel Rawlins <srawlins@google.com> > > Reviewed-by: Johnni Winther <johnniwinther@google.com> > > Reviewed-by: Joshua Litt <joshualitt@google.com> > > CoreLibraryReviewExempt: Relanding. > Change-Id: I40ff2a00682fccbd7dd44a364b5046aaac0f3bac > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/293203 > Reviewed-by: Joshua Litt <joshualitt@google.com> > Commit-Queue: Srujan Gaddam <srujzs@google.com> > Reviewed-by: Johnni Winther <johnniwinther@google.com> > Reviewed-by: Samuel Rawlins <srawlins@google.com> Change-Id: Ide8609575c73d714f3ae4f9ea9ffc74e228fa189 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/293962 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: Samuel Rawlins <srawlins@google.com> Reviewed-by: Leaf Petersen <leafp@google.com> Commit-Queue: Zach Anderson <zra@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.