Lasse R.H. Nielsen
b2f4cf3e01
The usual approach: Pure interfaces marked `interface`. Pure implementation classes marked `final`. Base classes marked `base` or nothing, and `mixin class` if reasonable. Combined X/XBase/XMixin where possible. CoreLibraryReviewExempt: Aske is away Change-Id: I927f9bd488fb385ff9c17c8fc94920a1f5076347 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/289200 Reviewed-by: Stephen Adams <sra@google.com> Reviewed-by: Slava Egorov <vegorov@google.com> Reviewed-by: Nate Bosch <nbosch@google.com> Commit-Queue: Lasse Nielsen <lrn@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.