Konstantin Shcheglov
f99d3628d1
Before we used a hack to request resolution information for a single library as needed, and requested kernels separately. This was hugely inefficient (but faster to implement as a steel thread). We had then recompile large library cycles many times, and take just one library. Before: 480 seconds to compile analyzer (ouch!). Now: 16 seconds (30 times faster). Without --previewDart2: 14 seconds. I will check why it is still slower later. R=brianwilkerson@google.com, paulberry@google.com Bug: Change-Id: Ic3d47684daa74c53f0336523e17b656f26328acf Reviewed-on: https://dart-review.googlesource.com/33144 Commit-Queue: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Paul Berry <paulberry@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
protocol is specified in the file analysis_server/doc/api.html.
Features and bugs
Please file feature requests and bugs at the issue tracker.