Brian Wilkerson
03a05b52d8
The element matcher threw a null check exception when getting a matcher in the argument list of a constructor redirect in a secondary constructor declaration with no explicit type name. This fixes it so that no exception will be thrown. That said, it isn't clear to me that this code could ever be reached outside of the tests. There might be a lot of unreachable code in ElementMatcher. I just can't prove that this particular bug would never have occurred. Change-Id: I5adf9ab5d4f79686110099054902a28535483f4d Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/505921 Reviewed-by: Samuel Rawlins <srawlins@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.