You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@alanz after thinking about this for a bit, I think the reason why it was not originally moved into haskell-lsp-types might have been that the wrapper types inside Language.Haskell.LSP.Messages aren't strictly a part of the LSP specification. They're types used only by haskell-lsp. Does it then make sense to leave them as a part of haskell-lsp? Or is it ok/used widely enough to consider moving into haskell-lsp-types?
Well, one argument is that the messages are part of the types.
My primary motivation for splitting them was to put all the TH stuff in a separate package that changed rarely, so working on haskell-lsp was not so achingly slow.
So using that criterion it should probably be called haskell-lsp-th-types, and we should try to limit them to that.
No description provided.
The text was updated successfully, but these errors were encountered: