Project
compiler
Describe the feature
The main motivation behind this is to use them in the LSP without much code duplication. Because the LSP processes files using the internal tooling of the compiler's older version, this is currently not possible in version 0.6.0-rc.0, because DependencyGraph is private. Also, we need to somehow extract information about the linearization order and paths that are hidden behind each file_id, so it would be nice to make Module public as well (and make getter for modules field in DependencyGraph).
I understand that exposing this interface might not be the best possible decision, so I would be happy to hear other solutions besides this.
Project
compiler
Describe the feature
The main motivation behind this is to use them in the LSP without much code duplication. Because the LSP processes files using the internal tooling of the compiler's older version, this is currently not possible in version 0.6.0-rc.0, because
DependencyGraphis private. Also, we need to somehow extract information about the linearization order and paths that are hidden behind eachfile_id, so it would be nice to makeModulepublic as well (and make getter formodulesfield inDependencyGraph).I understand that exposing this interface might not be the best possible decision, so I would be happy to hear other solutions besides this.