commit | c5eda0430fe37a268603a080b47d829d749c2f6b | [log] [tgz] |
---|---|---|
author | Ömer Sinan Ağacan <omersa@google.com> | Mon Feb 13 14:59:09 2023 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Feb 13 14:59:09 2023 +0000 |
tree | fdf1a1d1c46ba9af4bf2a541c9afad9ca023cbcf | |
parent | 54b2602b88e5bed241f7eda0ebe187a1c50b06d2 [diff] |
[dart2wasm] Implement records This generates a class for every record shape in the program. Record shape classes with the same number of fields share the same Wasm struct. (Shape is number of positional fields + set of names of the named fields) Summary of the changes: - A new kernel pass runs right before TFA and generates record shape classes for every record literal and type in the program, one class per shape. A class for a record shape has the name `Record_N_a_b_...` where `N` is the number of positional fields, and `a_b_...` is the `_` separated names of the named fields. For example, class for a record `(1, a: 'hi', false)` is: ``` @pragma('wasm:entry-point') class Record_2_a { @pragma('wasm:entry-point') final Object? $1; @pragma('wasm:entry-point') final Object? $2; @pragma('wasm:entry-point') final Object? a; @pragma('wasm:entry-point') Record_2_a(this.$1, this.$2, this.a); @pragma('wasm:entry-point') _Type get _runtimeType => // Uses of `runtimeType` below will be fixed with #51134 _RecordType( const ["a"], [$1.runtimeType, $2.runtimeType, a.runtimeType]); @pragma('wasm:entry-point') Type get runtimeType => _runtimeType; @pragma('wasm:entry-point') String toString() => "(" + $1 + ", " + $2 + ", " + "a: " + a + ")"; @pragma('wasm:entry-point') bool operator ==(Object other) { if (other is! Record_2_a) return false; if ($1 != other.$1) return false; if ($2 != other.$2) return false; if (a != other.a) return false; return true; } @pragma('wasm:entry-point') int hashCode => Object.hash(shapeID, $1, $2, a); } ``` `shapeID` in `hashCode` is unique to the class. It's not stored in the structs, only used in `hashCode` code. Field gets in members (`this.$1` etc.) are compiled to `struct.get`s as they're single target. `toString` currently does not use a buffer. This will be fixed in a separate CL. `entry-point` pragmas needed because there are no references from the program to these classes, but we want to consider them as potential targets. - When generating class infos, we have a special case for records to use the same struct for records with the same number of fields. - Code generator for record expressions get the record shape from the record type, and uses the struct type for the record. - `ProcedureAttributesMetadata` uses in dispatch table needs a special case for records. This is becuase as far as TFA concerned there's no connection from the program to the record shape class fields, so the it considers record shape class fields as not dynamically called. Fixes #50014. Change-Id: Ie8338a0917d51984a9e32e755ccdaa2783a8e2ba Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/280461 Commit-Queue: Ömer Ağacan <omersa@google.com> Reviewed-by: Aske Simon Christensen <askesc@google.com> Reviewed-by: Joshua Litt <joshualitt@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
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.