Add setting for multiple hie versions about vscode-haskell HOT 7 CLOSED

I see this eventually being handled on the server side. But in the interim the low hanging fruit is to do it in the client, like the hlint on/off setting

from vscode-haskell.

Do you want it to be similar to hlintOn in https://github.com/alanz/vscode-hie-server/blob/master/package.json#L79 ? Note that we can define enums in JSON schema.

from vscode-haskell.

I was wondering, as to make as little coupling to any editor, would it make sense for hie itself actually be a wrapper for hie-x.y.z, which is tied to the GHC version it was built for? Then hie would do its best to hit the right GHC version and then tunnel everything to that binary, while the editor configuration would then be for forcing a particular version? 🤔

My goal is in general to pack as much of the functionality in hie itself, so we don't loose any of the advantage we are seeing of editor plugins for hie being little more than "how to start the executable in with this particular LSP plugin".

from vscode-haskell.

I'll take a look

from vscode-haskell.

Wouldn't providing a package and requiring it to be built locally with stack solve this issue? If it's included in the stack snapshots it'd choose the right package automatically. Is it because we shouldn't assume someone uses stack?

from vscode-haskell.

I don't see how inclusion in stack snapshot helps us. And there are custom/local snapshots. And we need one hie per GHC. Requiring to rebuild hie whenever I change 9.14 to 9.15 and accumulation of some 20 versions of statically linked hie.exe and its dependencies are not good either.

from vscode-haskell.

Closed (as good enough) via haskell/haskell-ide-engine#447 and #41

from vscode-haskell.