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
Right now, the workspace mutex is only able to lock on write operations - any read operation will abort the current write operation. We want to extend the mutex to allow to perform a read operation (or multiple ones in parallel) after finishing all queued write operations.
This could also resolve the issue experienced in #1290, since it's probably related to an LSP service trying to resolve a cross reference during the build process.
The text was updated successfully, but these errors were encountered:
We decided to reduce it to a simple mutex because we wanted to keep things simple. At that time, I didn't see the case where a language developer adds a custom operation that needs read access at a point in time where the document is in a clean state. We could revive that old code now.
Right now, the workspace mutex is only able to lock on write operations - any read operation will abort the current write operation. We want to extend the mutex to allow to perform a read operation (or multiple ones in parallel) after finishing all queued write operations.
This could also resolve the issue experienced in #1290, since it's probably related to an LSP service trying to resolve a cross reference during the build process.
The text was updated successfully, but these errors were encountered: