| commit | 87b2f50c5c086844560fc1c8f1c08e41dedfd76d | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Tue Aug 19 07:33:37 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 19 07:33:37 2025 -0700 |
| tree | 16d8b75cbf4e1d2334ffad37c44e7786b05329c1 | |
| parent | 3175e427d83d00236c9fabf3ae8f95aa83774d6c [diff] |
[flow analysis] Align _attachFinally with the specification. This change refactors the `_attachFinally` method in `_FlowAnalysisImpl` to better align with the flow analysis specification. Notable changes include: - Moving `attachFinally` to the `FlowAnalysisImpl` class rather than implicitly passing the `afterTry` model as `this`. This makes the arguments to `attachFinally` match those in the spec. - Extracting the handling of a single variable to a separate function, `attachFinallyV`, to align with the spec. - Renaming local variables to match variable names in the spec. - Adding comments that refer to specific spec language. - Adding parenthetical "OPTIMIZATION:" comments to document differences between the implementation and spec that are for the purpose of efficiency and don't affect behavior. - Adding parenthetical "UNSPECIFIED:" comments to documented differences between the implementaiton and spec that reflect flow analysis features that haven't been documented yet. - Adding comments that directly reference the `attachFinally` and `attachFinallyV` sections of the specification. - Reordering logic to more closely follow the structure of the specification. This is a pure refactoring and does not change the behavior of flow analysis. Change-Id: I6a6a6964bd76b87102facf4251b195e5604c7c32 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/445780 Reviewed-by: Erik Ernst <eernst@google.com> Reviewed-by: Johnni Winther <johnniwinther@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.