Paul Berry
79974bb026
The spec uses the terminology "nullable", "non-nullable", etc. to refer to properties of types that differ subtly from their structure. For example "Null" is considered nullable, even though it lacks a trailing "?". Since we were using the Nullability enum to denote a purely structural property of types (whether they end in "?", "*", or neither), this led to confusion. So to avoid confusion, we rename the Nullability enum, and its enumerated values, to clarify that it refers specifically to the nullability suffixes and not to the property of being nullable/non-nullable. Change-Id: Ia34a500a3d2d724d30c66a410140ae11d6512f50 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/99275 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: 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
original protocol is specified in the file analysis_server/doc/api.html
and (less complete) 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.