| commit | 2f13e3d9a0c73737fb9d5ba6cc6643833dc1bc2b | [log] [tgz] |
|---|---|---|
| author | Sam Rawlins <srawlins@google.com> | Mon May 20 22:35:49 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 20 22:35:49 2024 +0000 |
| tree | b1455920b5ec80de6e5775b2bb049af01e92ecda | |
| parent | 14471930535728283ffa6a3550c519159c00791b [diff] |
DAS: Use an enum to express how broadly a CorrectionProducer can be applied We decided that the existing mechanism, three bool values that can be overridden by an AbstractProducer subclass, was confusing as it might give the impression that they are independent, and that any of the 8 possible combinations are valid. But really each author of a CorrectionProducer just needs to answer one question: how broadly can this correction be applied? So to answer that question we decided (loosely in emails) to offer an enum of a few values that more-or-less represent the sensible combinations of the bool getters. And more specifically I decided in this CL what those values should be. In this CL I also remove the notion of a default value. Each CorrectionProducer must indicate specifically how broadly it can be applied. This PR should functionally be a no-op; no applicability was increased or reduced. I left comments intact. I left `TODO(applicability)` comments where no comment is made to justify why a correction cannot be made any more broadly than "only at specific location." Change-Id: I3e3a12ee811b2b08f276ff755e7ff638f4fffabf Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/366740 Commit-Queue: Samuel Rawlins <srawlins@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@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.