Paul Berry
af1dbdf13b
Previously, this class held on to a ConstraintVariable indicating whether a null check should be inserted. Now it holds on to NullabilityNodes indicating whether the source and destination of an assignment are nullable, and it can infer from this whether a null check needs to be inserted. This paves the way for removing the old constraint solving logic in favor of a more direct nullability propagation approach using nullability nodes. Change-Id: I96b95c400ed40bd12f9c9dcbb4c09a69849e51c5 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/100885 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.