commit | 5510ef63a6dcd06423305e15e2014cf20ac94699 | [log] [tgz] |
---|---|---|
author | Paul Berry <paulberry@google.com> | Fri Dec 22 21:33:32 2023 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 22 21:33:32 2023 +0000 |
tree | ce127080426dd5c4c810dcdbc31776fd5e9051cb | |
parent | 4d3895a7b30155a9afc5e9ab06a69867cd5f262a [diff] |
Clean up shared Operations classes. The classes `Operations`, `TypeOperations`, and `VariableOperations` are reworked as follows: - The class `FlowAnalysisOperations<Variable, Type>` contains the API used by flow analysis to manipulate the client's representation of types and variables. This class (and the classes that support it) is located in `flow_analysis_operations.dart`, a sibling of `flow_analysis.dart`. - Note that `FlowAnalysisOperations<Variable, Type>` has a supertype, `FlowAnalysisTypeOperations<Type>`, which contains the portion of the API that is only concerned with types. This simplifies the implementation of flow analysis, by letting some of its lower-level operations be agnostic to how the client represents variables. - The class `TypeAnalyzerOperations<Variable, Type>` contains the API used by the shared type analyzer to manipulate the client's representation of types and variables. This class (and the classes that support it) is located in `type_analyzer_operations.dart`, a sibling of `type_analyzer.dart`. - Several abstract methods and getters that were previously in the `TypeAnalyzer` class are moved to `TypeAnalyzerOperations`, for consistency with `FlowAnalysisOperations`. Since the type analyzer calls out to flow analysis, the class `TypeAnalyzerOperations` is a subtype of `FlowAnalysisOperations`. This means that clients only need to implement a single API, `TypeAnalyzerOperations`. Change-Id: I7f33976d49bc998a7edd3f07f31576fe54886999 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/343280 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Chloe Stefantsova <cstefantsova@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 on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.