[analyzer] Find TODOs mainly without regex

The RegEx engine in the VM was updated in
e443b89f238cf97b7d33eb54ca34fc19ef44f52f which caused the analyzer
analyzing the CFE to use ~150 mio instructions more.

Part of this was an increased cost in TODO processing which relied on
regex.
The regex was long, complicated (and buggy) and the method scraping todo
comments (including children) when analyzing the CFE cost ~265 mio
instructions (up from ~191 mio instructions before the regex engine update) (numbers from `valgrind --tool=callgrind`).

This CL:
* Adds a test that didn't pass before.
* Removes the usage of the complicated regex with "normal code" that -
  while longer - is likely easier to debug in practice.
* Reduces the cost of scraping to ~92 mio (numbers from
  `valgrind --tool=callgrind`).

`perf stat` on this change with GC disabled goes from

```
    40,938,677,452      instructions:u
    40,935,421,892      instructions:u
    40,935,153,915      instructions:u
```

to

```
    40,756,218,191      instructions:u
    40,756,538,467      instructions:u
    40,756,528,402      instructions:u
```

A ~179 mio savings.

Change-Id: Id02c42d8be2ddbd24b96e33cc89320342efe7f4b
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/486800
Reviewed-by: Johnni Winther <johnniwinther@google.com>
Commit-Queue: Jens Johansen <jensj@google.com>
3 files changed
tree: 82a78d6ef08918a5939f7a322dfac6faca5a0743
  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.