| commit | 3e319ba752a77a9a970dd86944fa0508d2518e80 | [log] [tgz] |
|---|---|---|
| author | Phil Quitslund <pquitslund@google.com> | Fri Jan 05 05:07:10 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 05 05:07:10 2024 +0000 |
| tree | 3f1598b29a69a6cafc9ed034f3556a9de2936ae5 | |
| parent | 437767f4ae5adcd97186fb644761a6bed1ebccd0 [diff] |
Revert "options map support scaffolding in driver" This reverts commit 717ce7a69cfd190887181dfbe07d4bdeeec104d6. Reason for revert: breaking Google3 Original change's description: > options map support scaffolding in driver > > Konstantin and I chatted a bit about this so at least some of it shouldn't be too surprising to him but please do feel free to grab me to chat. > > That said a few pointers would be handy. Notably, this change: > > * introduces a new `SharedOptionsOptionsMap` for use in SDK drivers (and preserve current semantics) > * this is currently public but will be private once driver is more evolved to accommodate multiple options files > * removes the shared `_analysisOptions` from the analysis driver with a baby step to using the one shared in SharedOptionsOptionsMap > * removes context_builder and collection v2 experiments (and tests) > * I'll harvest some more functionality from these in future changes but for now they're distracting and hard to maintain > > This work is all to setup moving analysis options awareness into file state objects which will allow us to remove `sdkVersionConstraint` info from options (finally) and a host of other good stuff (see https://github.com/dart-lang/sdk/issues/54124). > > > > Change-Id: Ic4278184016d1018b4b5b1c6ac5ba9e2546927a5 > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/344860 > Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> > Reviewed-by: Konstantin Shcheglov <scheglov@google.com> > Commit-Queue: Phil Quitslund <pquitslund@google.com> Change-Id: Ia988c5c9cd328d0adce3d8e6ff019e389819a957 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/344960 Auto-Submit: Phil Quitslund <pquitslund@google.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
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.