| commit | e7658520bb4a88c95416ebe83abe59e329335bc6 | [log] [tgz] |
|---|---|---|
| author | MarkZ <markzipan@google.com> | Tue Aug 06 20:39:26 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 06 20:39:26 2024 +0000 |
| tree | 1caa797bd6ef171cb7d3563ede0dd989ebecced5 | |
| parent | b5330723862e1fdc9449e5fd17b7f628b96560f3 [diff] |
[ddc] Overhauling DDC's generic class representation. Prior to this change, DDC represented generic classes as closures over type parameters (with type arguments provided at runtime), which tightly coupled generic class definitions with their types and concrete instantiation. This rewrite decouples this representation, letting us 1) bind type information late and 2) separate generic class definitions from their instantiation. Notable changes: - Generic classes are now declared at top level (rather than within in closures). - RTIs are now passed to generic class constructors at runtime (except for JS Interop classes). Only the instantiated class's RTI is required (and it's retained up the type hierarchy). - Type signature resolvers are now lambdas that accept a type environment RTI at runtime. While signatures are still attached early, their instances' RTIs are now needed at runtime. - Generic classes, constructors, and factories are now evaluated in a 'Class' type environment. - An `RtiTypeEnvironment` is introduced to represent lookups on an RTI type environment bound to a parameter. These are used when evaluating type signatures and at constructor/factory bodies. - Type recipes now emit Class type parameters with names - but continue to emit method type parameters with de Bruijn indices. This is because indices aren't stable across subtypes. - Certain debugger functions now require instances (e.g.,`getClassMetadata`). - Adds a special flag for non-external JS interop factory constructors to emit 'true' types (versus 'any'). Change-Id: I7cbeaaf666dd4f9bd5e3ef22a1163a659fc0ee48 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/365863 Reviewed-by: Srujan Gaddam <srujzs@google.com> Reviewed-by: Kallen Tu <kallentu@google.com> Reviewed-by: Nicholas Shahan <nshahan@google.com> Reviewed-by: Nate Biggs <natebiggs@google.com> Commit-Queue: Mark Zhou <markzipan@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.