What would the smallest useful haskell-ide look like #4
Description
haskell-ide has a potentially very large scope.
A useful approach to managing this is to identify some useful, uncontroversial, small functionality that can test our architectural choices.
I think there are three broad categories of things that can be provided via haskell-ide
-
A place where a tool writer can host a tool as a plugin, and make use of standardised services to access the raw project and communication with the IDE, thus minimising this effort for all to get the tool integrated into multiple environments.
-
A way to query information about a project, and present it to the user. This in turn is a large topic, and can cover anything from contents of available libraries, to type information of loaded modules, to information to support syntax highlighting.
This may include on the fly error checking
-
Providing access to a REPL
So I suggest we come up with something from one of these categories, and aim to let it communicate with at least 2 different IDEs via the process identified in #2 / #3
What should these be?