analysis_server: Refactor disk reads for examples directory Fixes https://github.com/dart-lang/sdk/issues/50542 One primary principle is keeping the cost for _most code_ extremely low. Most code does not have an `examples/api` directory. Most comments do not have `{@tool`. Looking for directories on disk is expensive. Walking tokens in comment text is cheap. So we can pay the price of walking all comments, prowling for `{@tool` text which we won't likely find, and skip the work of looking for `examples/api` in _all_ parent directories, until we find a comment with `{@tool`. Don't check if `$parent/examples` exists before checking if `$parent/examples/api` exists. We don't care if `$parent/examples` exists. Don't create an `AanlyzerConverter` instance for _every element_ in a compilation unit while we are editing it. Instead, refactor some of the `AnalyzerConverter` methods to be extension methods. Change-Id: I812a1a435ee075e921782c1a57e9ed77325f9387 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/271863 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Samuel Rawlins <srawlins@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
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 is free and open source.
See LICENSE and PATENT_GRANT.
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).
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.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.