Brian Wilkerson
b402fac6fa
The two pieces of information we're tracking are - the number of libraries in each library cycle - the number of lines of code in each library cycle The data is reported in terms of percentage. This doesn't give us any way to correlate the two values. Knowing that there is a library cycle with M libraries and a cycle with N lines of code, doesn't tell us whether it's the same library cycle in both cases. Still, I think it will help us understand the nature of the code that we need to be able to analyze quickly. Change-Id: I36a8bf11c4c6fdced6c524225be7a633062351ac Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/437126 Reviewed-by: Keerti Parthasarathy <keertip@google.com> Commit-Queue: Brian Wilkerson <brianwilkerson@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 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.