Google Git
Sign in
dart / sdk / a7b1230e31f03775fb1e2bb708f9c42bb6a85b7d
commita7b1230e31f03775fb1e2bb708f9c42bb6a85b7d[log] [tgz]
authorJens Johansen <jensj@google.com>Wed Apr 10 11:22:00 2024 +0000
committerCommit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 10 11:22:00 2024 +0000
tree68d07c5db436ff5e8e7d2104c17c8d3959cbac04
parentc7834b676494a212e076da3fe39de38d663cbe5d [diff]
[CFE] Explicit creation script should work on part files

On presubmit we only run explicit creation on the changed files,
but if any of the changed files is a part that specified "part of" using
an identifier, and we don't otherwise compile that library, we won't
find it and will likely fail because of compilation errors.

This CL identifies such cases, scans the files in the package such a
file is in to find the library with that name, then replaces the part
file with the found file instead when doing the compilation.

This was especially annoying because updating `messages.yaml` would
update `codes_generated.dart` which specifies
`part of _fe_analyzer_shared.messages.codes;`. This should be fixed with
this CL.

Fixes https://github.com/dart-lang/sdk/issues/55236.

Change-Id: I299d5fc98fb3c9781b3134a2e1eff1055da26902
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/361840
Reviewed-by: Johnni Winther <johnniwinther@google.com>
Commit-Queue: Jens Johansen <jensj@google.com>
4 files changed
tree: 68d07c5db436ff5e8e7d2104c17c8d3959cbac04
  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 on our wiki.

Contributing to Dart

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

You can also contribute patches, as described in Contributing.