commit | 0c7585c907b5fae5fc6954628ec2732c029eadcb | [log] [tgz] |
---|---|---|
author | Paul Berry <paulberry@google.com> | Wed May 01 16:41:47 2024 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 01 16:41:47 2024 +0000 |
tree | 965854af01d410801014b128565dba7cfbfc0f40 | |
parent | 26a7b68ee624fe415060ad3003dc3b3d31bcc509 [diff] |
Start building a shared class hierarchy for types. This commit introduces the following new classes: - SharedType, which represents the common interface between the DartType classes in the analyzer and the CFE. - SharedRecordType, which represents the common interface between the RecordType classes in the analyzer and the CFE. - SharedNamedType, which represents the common interface between the analyzer and CFE representations of a name/type pair. - SharedUnknownType, which represents the common interface between the analyzer and CFE representations of the unknown type (`_`). This allowed three methods to be removed from the `TypeAnalyzerOperations` class: - `areStructurallyEqual`, which is replaced by `SharedType.isStructurallyEqualTo`. - `asRecordType`, which is no longer needed because `is SharedRecordType` can be used instead. - `isUnknownType`, which is no longer needed because `is SharedUnknownType` can be used instead. And one method to be removed from the `FlowAnalysisTypeOperations` class: - `isSameType`, which is replaced by `operator ==`. (Technically this could have been done even without introducing a shared class hierarchy, since `operator ==` is defined in the shared base class `Object`). The long term goal is to fill out the shared class hierarchy to cover other kinds of types (interface types, function types, void, etc.), and to move most of the shared logic from the analyzer and CFE DartType class hierarchies into shared code. This should reduce the risk of implementation skew between the analyzer and CFE, and to streamline the implementation of future features. Additionally, the hope is to eventually remove, or drastically simplify, classes like `TypeAnalyzerOperations`, so that the code in `_fe_analyzer_shared` can be written in simpler and more straightforward way. Change-Id: I5d3a929057959f77ccff8dbed5671f9bca6259c5 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/362481 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Chloe Stefantsova <cstefantsova@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 on our wiki.
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.