| commit | 814c61d88dd8404f1380d8a7d63e0cbe5761bc0c | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Tue Jul 01 06:00:30 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 01 06:00:30 2025 -0700 |
| tree | e175bf8cb64a9a528c22bff8e8efac351c25bfd0 | |
| parent | a7e6a9fd4d13a36f4d9a935912a056788ebc2f98 [diff] |
[analyzer] Don't import generated error code files more than needed. This change adds a `@Deprecated` annotation to each of the analyzer's generated error code files, with a deprecation message that says the corresponding non-code-generated file should be imported instead. For example, `package:analyzer/src/error/codes.g.dart` now has a deprecation message saying that `package:analyzer/src/error/codes.dart` should be used instead. All existing imports of these libraries are switched to the corresponding non-code-generated file, where possible. (The only circumstance in which it's not possible is when the corresponding non-code-generated file imports the code-generated file---e.g., when `package:analyzer/src/error/codes.dart` imports `package:analyzer/src/error/codes.g.dart`. In these cases, the deprecation warning is suppressed with an "ignore" comment.) This change is part of a long term effort to unify the analyzer and CFE representations of error messages. It paves the way for a follow-up CL in which I intend to move some of the generated code from `package:analyzer` to `package:_fe_analyzer_shared`, to allow it to be shared with the CFE. Change-Id: Ie91dc8fc9357defa8974cbe6836d582979d87d81 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/437840 Reviewed-by: Konstantin Shcheglov <scheglov@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.