tree-sitter-haskell
tree-sitter-haskell copied to clipboard
tree-sitter
Haskell grammar for tree-sitter.
For functions with a `do` block, the comments following the function get included in the function, for example: ``` f = do a -- | haddock g = b ```...
The `exp_lambda_case` node associated with the first definition includes the trailing white space:  This results, for example, in incorrect deletions when operating based off...
For instance, if we parse `examples/postgrest/test/Main.hs`: - using native, the top-level node is `haskell`; - using wasm, the top-level node is `ERROR`. In this case, the problem seems to be...
Changes: - add wasm tests to CI - use temporary workaround to get unpublished web-tree-sitter version - fix bugs in tree-sitter-parse.js
This package hasn't been published to npm in a while, and the most recently published version no longer compiles with the recent versions of tree-sitter. Would be possible to publish...
I was reading some GHC sources when I found my highlighting was broken. Here's a minimized example (which does compile with GHC): ```haskell module OhNo where lookupIdInScope :: Monad m...
I have done a run of executing tree-sitter-haskell against my employer Mercury's (closed source) codebase (350k LOC) and found a few parser bugs, which I have committed simplified testcases for...
Running ```shell tree-sitter highlight a.hs # or tree-sitter parse a.hs ``` with `a.hs` as ```haskell -- Fails data Aa = Bb | Cc | ``` Works just fine if `a.hs`...
The following piece of Haskell code is SOMETIMES incorrectly parsed as containing a series of top-level splices. ```haskell id :: a -> a id x = x const x y...
Not sure whether this is the right repo. But using NVim with [melange](https://github.com/savq/melange-nvim), the `Data.Text` part of these imports are colored differently: ``` import Data.Text (Text) import Data.Text qualified as...
