Brian Wilkerson
84beb4d31b
In addition to implementing the feature, this CL updates one of the contributors to use the new feature as a way of testing it. I haven't looked to see whether it impacts the metrics, but I wouldn't expect much change anyway because of the small number of completions that are likely to be effected by this change. It might be interesting to start thinking about ways to measure the impact of individual features. Change-Id: Idd0040a774e5fd9a6e3f6c29d0aa7fd762676fbe Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/143622 Commit-Queue: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Jaime Wren <jwren@google.com>
analysis_server
A long-running process that provides analysis results to other tools.
The analysis server is designed to provide on-going analysis of one or more code bases as those code bases are changing.
Using the server
The analysis server is not intended to be used stand-alone, and therefore does not have a human-friendly user interface.
Clients (typically tools, such as an editor) are expected to run the analysis
server in a separate process and communicate with it using a JSON protocol. The
original protocol is specified in the file analysis_server/doc/api.html
and (less complete) Language Server Protocol support is documented
in tool/lsp_spec/README.md.
Features and bugs
Please file feature requests and bugs at the issue tracker.