Allow language servers to store Client as struct field #199
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changed
LspService::new()
to accept anFnOnce(Client) -> T
closure instead of an already initializedT
value.&Client
parameters from allLanguageServer
trait methods.These changes should enable users to initialize
LanguageServer
implementers withtower_lsp::Client
conveniently stored as a struct field instead of having it passed into each callback method as an argument. Initialization would theoretically look like this:Additional resources required by the language server struct can be initialized ahead of time in
main()
and passed into the closure, if needed.CC @Timmmm @icsaszar
Closes #189.