[flow analysis] Add offset parameters to API.

Adds optional `offset` parameters to most flow analysis methods. Later
CLs will use these offsets to create a log of flow analysis state
changes, which can be later queried in order to determine the flow
analysis state at a given source code location.

A few new methods are added:

- `checkOffset`, which can be used by the client to help verify that
  the offsets it passes to flow analysis are sensible.

- `patternAssignment_beforeRhs`, which the client should call to
  inform flow analysis that it's about to visit the RHS of a pattern
  assignment expression.

- `patternForIn_beforeExpression`, which the client should call to
  inform flow analysis that it's about to visit the iterable
  expression in a pattern "for-in" statement or collection element.

- `patternVariableDeclaration_beforeInitializer`, which the client
  should call to inform flow analysis that it's about to visit the
  initializer of a pattern variable declaration.

The three new `pattern...` methods don't currently do anything, but
they will be needed once we try to populate the log. They will be
needed because in these three constructs, type analysis visits the
expression on the RHS _before_ it visits the pattern on the LHS. So if
the pattern match causes any promotions to occur, the log will need to
reflect the fact that those promotions are not in effect during
evaluation of the expression.

Part of https://github.com/dart-lang/sdk/issues/63816.

Change-Id: Ia920d708665e2bd85e84fc8cd7f826986a6a6964
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/529080
Reviewed-by: Chloe Stefantsova <cstefantsova@google.com>
Commit-Queue: Paul Berry <paulberry@google.com>
2 files changed
tree: f6865a542b2da0b03385958672d7dc645f9ee6d4
  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.