commit | 9d456bf516d7f8be6803051b0559926004c2832d | [log] [tgz] |
---|---|---|
author | Sam Rawlins <srawlins@google.com> | Wed May 04 01:05:05 2022 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Wed May 04 01:05:05 2022 +0000 |
tree | ec50d306a1ace6cded1ce1d6b6ea6c55fcee9914 | |
parent | ed7fd8a762fee921299ecf145bc7b1a04938b81c [diff] |
Basic client completion test This involves a large refactoring of completion_metrics.dart, extracting out some common code into completion_metrics_base.dart The code in completion_metrics.dart and completion_metrics_base.dart is largely unchanged, but restructured to fit the sub-class structure. * Rename CompletionMetricsComputer -> CompletionQualityMetricsComputer, as this is focused on quality metrics. * Extract out applyOverlay and removeOverlay methods. * Extract out computeSuggestionsAndMetrics, code which is run per ExpectedCompletion. * Extract out setupForResolution, for code custom to the quality computer. The meat of this change though is in completion_metrics_client.dart: * _AnalysisServerClient is code which was extracted from package:dartdev/src/analysis_server.dart. It may seem like an odd choice when we have package:analysis_server_client, but I think dartdev's client is fairly mature in creating a short-lived client, and handling crashes, etc. If this should be re-combined with dartdev, I think there are open questions about where that should live, and I'd like to address that in a follow-up. * The client does not perform overlays yet. * The client does not track slowest requests yet. * The client does not have support for performance metrics which DAS tracks itself. Adding this is high priority. Change-Id: Ib259f78e4646d10b61559bfd5700d98a95d14d43 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/243522 Commit-Queue: Samuel Rawlins <srawlins@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@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.