4 ms·
Yes I understand, but do you not have issues that it drifts out of date and confuses the agents (especially on longer running tasks)? Like even "full" Visual S
by martinald 5mo ago
Yes I understand, but do you not have issues that it drifts out of date and confuses the agents (especially on longer running tasks)?
Like even "full" Visual Studio and Resharper have issues with this. Eg, you start editing file x, 'intellisense' runs, says there are loads of errors... because you haven't finished editing yet.
- tuo-lei 5mo agosame issue from the other side. when a human is editing, the LSP fires mid-keystroke and shows bogus errors for a second, whatever. with an agent doing 5 edits in a row, the symbol DB is always behind by one edit, so the next lookup pulls stale references. you can re-index synchronously after each edit but that kills the batching speed.
- GodelNumbering 5mo agoIt does a before/after comparison. Fetch the LSP error state, apply all edits, fetch it again, diff