| commit | 082c71062b9e924ac7cb6f8e5eec9e3647112949 | [log] [tgz] |
|---|---|---|
| author | Sam Rawlins <srawlins@google.com> | Thu Nov 07 18:49:01 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 07 18:49:01 2024 +0000 |
| tree | 8cc799775afd23a235ee857940285cc4dcc001d3 | |
| parent | e7c0452249535f8371df08cb9b01f8a6c76bb77d [diff] |
analyzer: Move enableTiming out of AnalysisOptionsImpl to AnalysisDriver. It has seemed disingenuous to me that `enableTiming` has been a property of AnalysisOptionsImpl, when it cannot be specified in an analysis options file. Additionally, it is used in exactly _one_ place: the linter package's `benchmark.dart` script. Instead, it makes more sense to think of this "flag" as a process-wide flag. It is not something that may be set one way for some files, and another for another set of files. And it is not something that can be set to one value early during an analysis process, and then change; it never changes. So instead this change makes it a _final_, _private_ field on AnalysisDriver, and on LibraryAnalyzer. LibraryAnalyzer gets its value from AnalysisDriver, and AnalysisDriver gets its value from the AnalysisContextCollectionImpl constructor. Change-Id: I347605775680a8ea1c1237f0ee20bd4bbe2c6216 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/393961 Reviewed-by: Phil Quitslund <pquitslund@google.com> Commit-Queue: Samuel Rawlins <srawlins@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 in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.