[front end] Take over responsibility for tracking expression info.

Shifts the responsibility for tracking the flow analysis
`ExpressionInfo` objects from the shared `FlowAnalysis` class to the
analyzer's `FlowAnalysisHelper` class.

This is a step towards a long term plan for the front end to pass
these `ExpressionInfo` objects around on the stack: the code that
resolves an expression will return that expression's `ExpressionInfo`
(among other data), and the code that resolves the expression's parent
will plumb the data to the appropriate flow analysis method. This
should be much less error prone than the current approach of keeping
track of a map from `Expression` to `ExpressionInfo`, since we won't
have to be careful about updating the map when rewriting the AST. It
should also be more efficient, since it will avoid costly map lookups.

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