Query-Based Compiler Architectures

Re:Query-Based Compiler Architectures by matklad on Friday June 26, 2020 @03:04AM (#23649483)

I am not the author, but work in the same domain. Empirically, existing compilers are impossible to turn into good IDEs, unless the language has header files and forward declarations. Otherwise, you get a decent IDE by doing one of the following:

* writing two compilers (C#, Dart, Java(and, in some sense, every major language, supported in JetBrains tooling)

* starting with IDE compiler from the start (Kotlin & TypeScript)

The two examples where I’ve heard a batch compiler was successfully used to build a language server are C++ and OCaml (haven’t tried these language servers myself though). Curiously, they both use header files, which means that it’s the user who does fine grained caching.

I don‘t see how caching in LLVM is relevant to the task of building LSP servers.

In terms of prior art, I would suggest studying how IntelliJ works, specifically looking at the stubs:

https://www.jetbrains.org/intellij/sdk/docs/basics/indexing_...

[ Parent | on HN ]

Re:Query-Based Compiler Architectures by seanmcdirmid on Friday June 26, 2020 @03:40AM (#23649670)

There are ways to turn batch compilers into incremental IDE compilers with some tree and effect caching on the periphery of the compiler. You can even go all the way up to the eval level for a full live programming environment. You don’t need module signatures if you are willing to trace dependencies dynamically.

See https://www.microsoft.com/en-us/research/publication/program....

[ Parent | on HN ]