| commit | 435a56bccccb57d91c623eff31060677d455f0c2 | [log] [tgz] |
|---|---|---|
| author | Kallen Tu <kallentu@google.com> | Mon Dec 01 10:16:23 2025 -0800 |
| committer | Kallen Tu <kallentu@google.com> | Mon Dec 01 10:16:23 2025 -0800 |
| tree | d89b71a9adb5d8ada195c02cca88dd148748f2cc | |
| parent | 13351c15981f02542a1ba8bff908498ba048f7a8 [diff] |
[analyzer] Dot shorthands: Tests with abstract classes, factory constructors, const ctors, and type arguments. Testing the code paths of `InstanceCreationExpressionResolver.resolveDotShorthand`. I wanted to make sure we covered everything with these conditions so this is a sanity check to make sure the recent changes with https://dart-review.googlesource.com/c/sdk/+/462542 still kept the same semantics. The only big difference that I can see with the change above is that `test_abstractClass_const_typeArguments` has two diagnostics instead of one now. I checked with the equivalent non-shorthand code, and we are also producing two diagnostics, so I'm not too bothered by that. This is a table of what each unit test is testing. Abstract Factory Const Type args Analyzer Test FALSE FALSE FALSE FALSE Most existing tests FALSE FALSE FALSE TRUE test_typeParameters FALSE FALSE TRUE FALSE Existing const ctor tests FALSE FALSE TRUE TRUE test_typeParameters_const FALSE TRUE FALSE FALSE test_factory FALSE TRUE FALSE TRUE test_factory_typeArguments FALSE TRUE TRUE FALSE test_factory_const FALSE TRUE TRUE TRUE test_factory_const_typeArguments TRUE FALSE FALSE FALSE test_abstractClass TRUE FALSE FALSE TRUE test_abstractClass_typeArguments TRUE FALSE TRUE FALSE test_abstractClass_const TRUE FALSE TRUE TRUE test_abstractClass_const_typeArguments TRUE TRUE FALSE FALSE test_abstractClass_factory TRUE TRUE FALSE TRUE test_abstractClass_factory_typeArguments TRUE TRUE TRUE FALSE test_abstractClass_factory_const TRUE TRUE TRUE TRUE test_abstractClass_factory_const_typeArguments Bug: https://github.com/dart-lang/sdk/issues/61978 Change-Id: I6be2df562711cd7e8f52dacf62a422b823afdad1 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/464764 Reviewed-by: 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.