Google Git
Sign in
dart / sdk / e5739ab46686b849fa727d71bc34791144a5c0a2
commite5739ab46686b849fa727d71bc34791144a5c0a2[log] [tgz]
authorPaul Berry <paulberry@google.com>Wed Nov 20 00:26:10 2024 +0000
committerCommit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Nov 20 00:26:10 2024 +0000
tree796fafcb05b92be96d10fc45483730c20a76c1c0
parent90cd440fe131d6ce4f8a114aecd65f756dcf5e4e [diff]
[analyzer] Rework MockSdkElements to set enclosing elements earlier.

In the typical sequence of operations performed by the analyzer, an
element's chain of enclosing elements is guaranteed to be set before
that element is referred to by any `DartType`-derived objects. In a
follow-up CL, I will be adding some error checking to the unnamed
constructor of `InterfaceTypeImpl` that relies on this ordering
guarantee.

This change reworks `MockSdkElements` so that it also follows this
ordering guarantee. This will ensure that when the error checking is
added to `InterfaceTypeImpl`, it won't break tests that use
`MockSdkElements`.

This change has no visible effect on the analyzer behavior, since it
only touches test code.

Change-Id: Ibb60575578a8b3facb4014d3583eed23db2ff694
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/396521
Commit-Queue: Paul Berry <paulberry@google.com>
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
1 file changed
tree: 796fafcb05b92be96d10fc45483730c20a76c1c0
  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.