Danny Tuppeny
619f2995ab
* Add empty closing labels computer/visitor and tests. See #30285 * Add initial implementation and test for closing labels. See #30285 * Add various tests for analyzer closing labels. See #30285 * Fail tests if errors occur. Without this the notifications will never come through and the test will time out. This causes them to fail right away on errors. See #30285 * Add test and fix for crash that occurred during testing. See #30285 * Remove unnecessary abs(). See #30285 * Remove question that has been answered (yes). See #30285 * Remove unnecessary .argumentList on spansManyLines check. See #30285 * Add test for prefixed import and constructor names. The behaviour seems like what we want, though need to confirm if this is the best way to do it. See #30285 * Add additional prefixed tests and another TODO. See #30285 * Fix method invocations to show full target/name. See #30285 * Fix constructor invocations to not use toString(). See #30285 * Convert most closing label tests to unit tests. See #30285
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
protocol is specified in the file analysis_server/doc/api.html.
Features and bugs
Please file feature requests and bugs at the issue tracker.