This means reloading a database, and providing an updated version for all passes.
Ideally we would like to provide functions which a server could use to support to LSP protocol, even though such a server would be outside of the scope of this library.
Interestingly, LSP provides document synchronization with a notification each time a document changes. This could allow incremental passes over the database, where e.g only the segment which have changed would be rebuilt.
However this also requires to be well thought within the library (e.g. Atom numbering would change with an incremental build).
SMM provided some functionality and/or provision for this.
This means reloading a database, and providing an updated version for all passes.
Ideally we would like to provide functions which a server could use to support to LSP protocol, even though such a server would be outside of the scope of this library.
Interestingly, LSP provides document synchronization with a notification each time a document changes. This could allow incremental passes over the database, where e.g only the segment which have changed would be rebuilt.
However this also requires to be well thought within the library (e.g.
Atomnumbering would change with an incremental build). SMM provided some functionality and/or provision for this.