Reporting error diagnostics by using `c3c build --test`

[pherrymason]

By calling c3c build --test on the project, LSP could get some initial diagnostics showing compiler errors as the user modifies its project.

• [x] Run diagnostics on project open and document modifications.
• [x] Delay running diagnostics for X seconds after every document modification.
• [x] Include new option to specify path to c3c: c3c-path
• [x] Include new option to specify with what delay the diagnosis should be executed: diagnostics-delay
• [x] Disable diagnostics:
  • [x] if client does not support it.
  • [x] If using a wrong c3c version (one prior to the fix of absolute paths and missing character number)

Reference: https://github.com/c3lang/c3c/issues/1329

[joshring]

In order to fix this locally I moved

state.SetCalculateDiagnostics(true) inside of runDiagnostics to it's first line

[joshring]

though that lead to a regression in behaviour

[nikpivkin]

Hi @pherrymason ! @joshring is right, since calculatingDiagnostics is set when diagnostics is run, subsequent calls to diagnostics cannot override the previous one. Does this boolean flag make sense if debouncing is used?

[pherrymason]

You are both right, calculatingDiagnostics is causing the bad behaviour. I removed its usage completely as @nikpivkin is right, it might not be needed if I'm already using a debounce. Thank you!