You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is some perceived slowness in diagnostics because we always compute syntactic and semantic diagnostics before reporting anything to the client in document pull. It can take a bit to compute semantic diagnostics which is expected. However, we can generally compute syntax diagnostics fairly quickly and in the old system we would push those first so that they show up fast.
Document pull supports streaming, so we should compute the syntax diagnostics first, send a report, while we are still waiting for semantic diagnostics to be computed.
The text was updated successfully, but these errors were encountered:
FWIW Visual Studio's LSP client supports progressive notifications in document diagnostics but it doesn't actually update the UI until all of the notifications have landed.
FWIW Visual Studio's LSP client supports progressive notifications in document diagnostics but it doesn't actually update the UI until all of the notifications have landed.
Reported by @CyrusNajmabadi
Currently there is some perceived slowness in diagnostics because we always compute syntactic and semantic diagnostics before reporting anything to the client in document pull. It can take a bit to compute semantic diagnostics which is expected. However, we can generally compute syntax diagnostics fairly quickly and in the old system we would push those first so that they show up fast.
Document pull supports streaming, so we should compute the syntax diagnostics first, send a report, while we are still waiting for semantic diagnostics to be computed.
The text was updated successfully, but these errors were encountered: