[analyzer] Change InheritanceManager3 to use Impl types.

The following methods of `InheritanceManager3` are changed so that
their return types refer to Impl classes rather than analyzer public
API classes:

- `combineSignatures`
- `getInherited2`
- `getInheritedMap2`
- `getMember`
- `getMember2`

To reduce the number of type casts this introduces, some of the
parameters and return types of various private methods of
`InheritanceManager3` are also changed to use Impl types, and some
similar changes are made to the inheritance manager's internal data
structures (`Interface` and `_ExtensionTypeCandidates`).

Also, the following new classes are introduced, to act as common base
classes for analyzer-internal classes in situations where no common
base class previously existed:

- `ExecutableElementOrMember` (the common base class for all internal
  classes that implement `ExecutableElement`)

- `PropertyAccessorElementOrMember` (the common base class for all
  internal classes that implement `PropertyAccessorElement`)

- `PropertyInducingElementOrMember` (the common base class for all
  internal classes that implement `PropertyInducingElement`)

- `VariableElement2OrMember` (the common base class for all internal
  classes that implement `VariableElement2`)

- `VariableElementOrMember` (the common base class for all internal
  classes that implement `VariableElement`)

This is part of a larger arc of work to change the analyzer's use of
the shared code so that the type parameters it supplies are not part
of the analyzer public API. See
https://github.com/dart-lang/sdk/issues/59763.

Change-Id: Ib7f20480c1f57af22a0214075e8f0e13c3429340
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/405565
Commit-Queue: Paul Berry <paulberry@google.com>
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
8 files changed
tree: bfccf816dd3be53972a0e507538b5ea628a18e3c
  1. .dart_tool/
  2. .github/
  3. benchmarks/
  4. build/
  5. docs/
  6. pkg/
  7. runtime/
  8. samples/
  9. sdk/
  10. tests/
  11. third_party/
  12. tools/
  13. utils/
  14. .clang-format
  15. .gitattributes
  16. .gitconfig
  17. .gitignore
  18. .gn
  19. .mailmap
  20. .style.yapf
  21. AUTHORS
  22. BUILD.gn
  23. CHANGELOG.md
  24. codereview.settings
  25. CONTRIBUTING.md
  26. DEPS
  27. LICENSE
  28. OWNERS
  29. PATENT_GRANT
  30. PRESUBMIT.py
  31. README.dart-sdk
  32. README.md
  33. sdk.code-workspace
  34. sdk_args.gni
  35. sdk_packages.yaml
  36. SECURITY.md
  37. WATCHLISTS
README.md

Dart

An approachable, portable, and productive language for high-quality apps on any platform

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 platforms illustration

License & patents

Dart is free and open source.

See LICENSE and PATENT_GRANT.

Using Dart

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).

Building Dart

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.

Contributing to Dart

The easiest way to contribute to Dart is to file issues.

You can also contribute patches, as described in Contributing.

Roadmap

Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.