Google Git
Sign in
dart / sdk / 82a59fe398949fdf71ff815bc8a866b86920f5b5
commit82a59fe398949fdf71ff815bc8a866b86920f5b5[log] [tgz]
authorPaul Berry <paulberry@google.com>Wed Sep 24 15:21:30 2025 -0700
committerCommit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Sep 24 15:21:30 2025 -0700
tree65bdf65c87b2c36440cd91bbae995222241e69be
parent305189ec8f31df92893192ff482e3e6c8fff52dc [diff]
[analyzer] Introduce `experimental_member_use` warning.

In a follow-up CL, I will add logic to report this warning if
reference is made to an element annotated with `@experimental`.

In order to do that without causing trybot failures, I will need a
preparatory CL that add some analysis_options directives to ignore the
new warning in places where it's expected.

But the analyzer contains logic to warn if an unknown diargnostic code
is referenced from an analysis_options file. So to avoid that
preparatory CL causing trybot failures, I need to first add the
warning code itself, which is what this CL does.

Change-Id: I6a6a69642c1487bf765b49f0e73c6e8468615fcc
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/451341
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
Commit-Queue: Paul Berry <paulberry@google.com>
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
4 files changed
tree: 65bdf65c87b2c36440cd91bbae995222241e69be
  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. pubspec.yaml
  32. README.dart-sdk
  33. README.md
  34. sdk.code-workspace
  35. sdk_args.gni
  36. sdk_packages.yaml
  37. SECURITY.md
  38. 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.