Why building a Rust LSP is hard

(rust-glancer.github.io)

12 points | by agluszak 2 days ago

2 comments

  • mitxela 23 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.
  • octoberfranklin 8 minutes ago
    Enter hell: LSP assumes that it's the source of truth, but you still need to access the filesystem yourself, and do it in a synchronized way

    LSP is an example of utterly horrid technical design.

    Stop letting Microsoft design protocols and APIs. They are so. bad. at. it.

    • duttish 6 minutes ago
      I've never looked into LSP, how would you design it?
      • mitxela 4 minutes ago
        Start with synchronous function calls instead of JSON. Microsoft knows how to do that - they invented COM.
      • packetlost 5 minutes ago
        Well for one I wouldn't design it so both the LSP and the editor need a synchronized view of the underlying file.