As one of the authors of https://hsyl20.fr/home/files/papers/2022-ghc-modularity.pdf https://hsyl20.fr/home/files/papers/2022-ghc-modularity.pdf (discuessed at

As one of the authors of https://hsyl20.fr/home/files/papers/2022-ghc-modularity.pdf https://hsyl20.fr/home/files/papers/2022-ghc-modularity.pdf (discuessed at https://news.ycombinator.com/item?id=31250141 https://news.ycombinator.com/item?id=31250141) this rings really true. If all we do is compiled and to end, it is really easy for the pipeline stages to "rot together" such that we get these lies the blog post author points out. We must to be able to start and resume compilation from any point, with arbitrary programs in the intermediate representation to ensure modularity doesn't regress. Really glad IDE and now security use-cases are finally hammering these basic software arch principles to compiler writers! I recall and earlier thread, https://discourse.llvm.org/t/rfc-an-mlir-based-clang-ir-cir/63319 https://discourse.llvm.org/t/rfc-an-mlir-based-clang-ir-cir/..., where someone else was interested in the same thing. And it seems Vast (prior to open sourcing, and the reveal of that name) was mentioned by the blog post author in the thread. Very much hoping there is thus enough interest to get this upstreamed. Best of luck to everyone involved!