Jens Johansen
90fb141aa2
Before an assist call on a file with non-windows lineendings would first search through the entire file for Windows line endings, then search for the non-Windows line endings. As such Windows line endings was faster. This CL changes the semantics slightly from "Windows line endings if any Windows line endings exist" to "whatever line endings are first used" which should be good. It speeds up assist calls with non-Windows line endings: Statistics on 5 runs each: ``` Windows / 2000: No change. Windows / 4000: No change. Windows / 8000: No change. Unix / 2000: 1000 assist calls: -46.9900% +/- 6.1715% (-0.88 +/- 0.12) (1.86 -> 0.99) Unix / 4000: 1000 assist calls: -59.1561% +/- 6.3982% (-1.79 +/- 0.19) (3.03 -> 1.24) Unix / 8000: 1000 assist calls: -63.8429% +/- 4.3083% (-3.68 +/- 0.25)(5.76 -> 2.08) ``` Change-Id: I61278ed4ad31b891e87951da0a6162fe37376888 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/437224 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Jens Johansen <jensj@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.