Diagnostics

[z80dev]

For any given contract, we want to report to the user as many compilation errors and warnings as possible.

This will allow users' editors to display these errors clearly when rendering contract source code.

Implementation note: if a language is single file only (for example HTML) then diagnostics are cleared by the server when the file is closed.

This supports both Errors and Warnings, such as deprecated language features (things like ZERO_ADDR which have been replaced by empty(address))

LSP API Methods

• textDocument/publishDiagnostic

Handling Multiple Errors

While the compiler will only report one error as the cause for a failure in compilation, it is possible we may be able to evaluate the contract by some other heuristic and detect additional errors not reported by the compiler as a cause for compilation failure.