Konstantin Shcheglov
983b3a8b85
IIRC it was added in https://dart-review.googlesource.com/c/sdk/+/45922 only to see if an optional positional formal parameter is used, and is not used otherwise anywhere else in DAS. I think that the usefulness of this feature is limited, and not indexing optional positional would be consistent with handling of required positional formal parameters. I have also similar thoughts about `super.foo` references from required or optional positional formal parameters of constructors. As with these, we have to filter them out during refactoring, again without obvious usefulness to balance it. Change-Id: I7eed423bb9d83ae78ce0cac6625eae79a7240316 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/475960 Reviewed-by: Samuel Rawlins <srawlins@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@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.