| commit | 7f5a698514bce37fed78f8c78046f6f37d8d5fdc | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Mon Aug 19 16:09:14 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 19 16:09:14 2024 +0000 |
| tree | 7bf07a66f5706b504b14664c44d2806a693c124a | |
| parent | 8becafbe571a1ba0399d11d0c826d4648e2cddf1 [diff] |
UNREACHABLE_SWITCH_CASE: Remove HintCode in favor of WarningCode. Previously, `HintCode.UNREACHABLE_SWITCH_CASE` was marked as deprecated, and `WarningCode.UNREACHABLE_SWITCH_CASE` was an alias to it. This created a slightly confusing situation, because it meant that all code referring to the diagnostic had to refer to it as `WarningCode.UNREACHABLE_SWITCH_CASE` (to avoid a deprecation lint), but the diagnostic still _behaved_ like it was a hint, and therefore test runner expectations still had to treat it as a hint. It turns out that it's not really necessary to go through the deprecation dance when changing the kind of a diagnostic, since (a) members of `HintCode` and `WarningCode` aren't exposed through the analyzer public API, and (b) ignore comments don't have to specify whether something is a hint or a warning. So the easiest way to clear up the confusion is to just remove `HintCode.UNREACHABLE_SWITCH_CASE` entirely, and move its implemention into `WarningCode.UNREACHABLE_SWITCH_CASE` (so that the latter is no longer an alias). Change-Id: I9ff7901ad38a2c168c5e54cbe0c1c52bf7c50186 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/381103 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Samuel Rawlins <srawlins@google.com> Commit-Queue: Paul Berry <paulberry@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.