Why building a Rust LSP is hard

(rust-glancer.github.io)

13 points by agluszak2 days ago

2 comments

  • mitxela35 minutes ago
    Using a JSON TCP connection for what on Windows would be direct function calls (COM) or in Eclipse would be direct function calls between Java modules always felt a bit gross.
  • octoberfranklin20 minutes ago
    <i>Enter hell: LSP assumes that it&#x27;s the source of truth, but you still need to access the filesystem yourself, and do it in a synchronized way</i><p>LSP is an example of utterly horrid technical design.<p>Stop letting Microsoft design protocols and APIs. They are so. bad. at. it.
    • duttish19 minutes ago
      I&#x27;ve never looked into LSP, how would you design it?
      • mitxela17 minutes ago
        Start with synchronous function calls instead of JSON. Microsoft knows how to do that - they invented COM and OLE. Function calls enable whatever data sharing is necessary to maintain a coherent view. Imagine trying to do OLE with JSON - just wouldn&#x27;t work. (Does OLE still exist?)
      • packetlost17 minutes ago
        Well for one I wouldn&#x27;t design it so both the LSP and the editor need a synchronized view of the underlying file.