| commit | a226405a70c31a418be2243487d8d3882fa5e03e | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Thu Jun 12 20:45:35 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 12 20:45:35 2025 -0700 |
| tree | d96b8b71172a38fac6285f04f63b9ac3a69fbf61 | |
| parent | ff19bdba8a64e2d0b2fb1261a68c49da7103029a [diff] |
[flow analysis] Improve how catch clauses are modeled in tests. This change updates the mini_ast testing infrastructure so that: - It properly models the "exception type" part of a catch clause (the type named after the `on` keyword). - It requires an exception variable to be specified if there is a stack trace variable (this is required by the Dart grammar). - It requires an exception type to be specified if there is no exception variable (this is required by the Dart grammar). - During the "pre-visit" stage, the exception variable and stack trace variable are registered with the `AssignedVariables` object, so that they can be properly handled by type promotion. - During the main "visit" stage, the exception variable and stack trace variable are assigned the appropriate types. Flow analysis unit tests are updated in order to meet the new requirements, and flow analysis tests are added to check that stack trace and exception variables are promotable and appropriately typed. By ensuring that stack trace and exception variables are properly typed during flow analysis tests, this paves the way for some follow-up work, in which I plan to re-work how flow analysis keeps track of variable types. There is no behavioral change to the analyzer or compiler pipeline; these changes are confined to `pkg/_fe_analyzer_shared/test`. Change-Id: I49c4b894d82d1dc58d62e3d3f25d232c9106922e Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/434145 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: 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 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.