[tests] Primary constructors - Tests on assignment, naming conflicts, and more. Language tests for the following: - A compile-time error occurs if an assignment to a primary parameter occurs in the initializer list of the body part of a primary constructor. - A compile-time error occurs if an instance variable declaration has an initializing expression, and it is also initialized by an element in the initializer list of the body part, or by an initializing formal of the primary constructor. - The modifier `final` on a parameter in a declaring constructor specifies that the instance variable declaration which is induced by this declaring constructor parameter is `final`. - A compile-time error occurs if a class, enum, or extension type has a primary constructor whose name is also the name of a constructor declared in the body. - Extension types are allowed to have non-redirecting generative constructors, implicitly or explicitly initializing the representation variable. - A compile-time error occurs if a class, mixin class, enum, or extension type declares a primary constructor whose name is `C.n`, and the body declares a static member whose basename is `n`. - Consider a factory constructor declaration of the form `factory C(...` optionally starting with the modifier `const`. Assume that `C` is the name of the enclosing class, mixin class, enum, or extension type. In this situation, the declaration declares a constructor whose name is `C`. The rule which is being tested here is also applicable when the declaration has some of the keywords external and augment, but we don't test those kinds of constructors here. - It is an error to have multiple primary constructor bodies. - Tests for type inference of declaring parameters in primary constructors, including override inference and inference from default values. Bug: https://github.com/dart-lang/sdk/issues/61687 Change-Id: If804c99c317ab53643420e00d6dc266720bca2f1 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/483626 Commit-Queue: Kallen Tu <kallentu@google.com> Reviewed-by: Erik Ernst <eernst@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.