| commit | 72c2e73f0b195d2daf4739ac8be0ba27e3633ff0 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Thu Sep 26 13:32:20 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 26 13:32:20 2024 +0000 |
| tree | 5af59de8f973fcd47de96467d7d8074dcf2c5b1b | |
| parent | 32b00bb42c85f33ed65f3732a47d2906cc43f5b5 [diff] |
Fill out return type of TypeAnalyzerOperations.matchTypeDeclarationType The return type of this method was previously `TypeDeclarationMatchResult?` (with no explicit type arguments), meaning that the generic type parameters of `TypeDeclarationMatchResult` would be filled in by instantiate-to-bounds as `Object, Object, Object`. But the implementations always return the more precise type `TypeDeclarationMatchResult<TypeDeclarationType, TypeDeclaration, TypeStructure>?`, and the use sites all expect this type. Adding explicit type arguments improves type safety and probably allows the compiler to elide some of the type casts involved in pattern matching. Also, the "mini_ast" implementation of this method contained a subtle bug: instead of using `unwrappedType.type` for the `typeDeclaration` Change-Id: Ic7bffc1b0b3e9bfc86c0168d4e6bdf442af8ae39 argument, it should use `unwrappedType.name`. This ensures that if the type being matched is generic, the generic arguments don't show up in the `typeDeclaration`. Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/386681 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 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.