[analyzer] Dot shorthands: Remove error when a constructor conflicts with a non-static member. Users are getting an extra error when a constructor and an instance method/getter have the same name. In the implementation, we produce an error once we see that the retrieved dot shorthand element isn't static. Instead, we should be falling through to check for constructor elements of that name. This CL makes the necessary changes. Testing: `element != null && element is InternalExecutableElement && element.isStatic` is tested by existing tests. `element != null && element is InternalExecutableElement && !element.isStatic` is tested in the `test_conflict_instance_*` unit tests. This is the behavior with the bug. `element != null && element is! InternalExecutableElement` should not exist since the `_resolveElement only returns `ExecutableElement`s or `null`. (There's definitely something we can refactor here, but I'll leave it for a future CL.) If we can't find a static method/field of that name, we should be checking if it's the name of a constructor for both of the above cases. `element == null` occurs when we can't find any method/getter of a given name. If there's a setter of the given name, this will be `true` as well. This is well tested by prior unit tests. Fixes: https://github.com/dart-lang/sdk/issues/62045 Change-Id: Icc6b66a95cfc79312891453b6f277f1347e059bc Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/467261 Commit-Queue: Kallen Tu <kallentu@google.com> 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.