| commit | d746c5f941f6cdaec5ed03336cc422742d8f1d92 | [log] [tgz] |
|---|---|---|
| author | Ömer Sinan Ağacan <omersa@google.com> | Fri Nov 01 13:30:40 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Nov 01 13:30:40 2024 +0000 |
| tree | a2cbf78af6c11034a8b10d1a59ebd57656cdbbb5 | |
| parent | 2bcb7361d536de5e2ce7e1e9bf4a1900afaa68d3 [diff] |
[dart2wasm] Some refactoring around context and capture generation
This mainly refactors code that use the `Closures` type to make it a bit
more clear what it does and how it does it, and make it more difficult
to misuse.
Changes:
- Make `CaptureFinder`, `ContextCollector`, `Closures.findCapures`,
`Closures.collectContexts`, `Closures.buildContexts` private.
It doesn't make sense to use these types outside, and the `Closures`
members need to be called together and in the right order. Make them
private and call them in the constructor.
Reduces API surface of `closures.dart` and makes it easier to use.
- Document all public members of `Closures`.
- Remove unused `ClosureRepresentation.exportSuffix`.
- In `TearOffCodeGenerator`, inline the single-use function
`generateTearOffGetter`. Makes it clear that the code is not reused
elsewhere.
- Make the type of `Types.nonNullableTypeType` more precise. Use it in
`closures.dart` instead of having a separate copy of the same thing.
- In a few places where we had function body entirely guarded with an
`if`, add an early return.
For example:
```
void f() {
if (x) { ... lots of code ... }
}
```
Becomes:
```
void f() {
if (!x) return;
... lots of code ...
}
```
Similarly do it in loop bodies.
Change-Id: Ia2a74b89ae311b8f32b9f1a4e72c51d4ea3861e8
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/392942
Reviewed-by: Martin Kustermann <kustermann@google.com>
Commit-Queue: Ömer Ağacan <omersa@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.