-
Once #4 is finished, we want to parse it - let's track related problems here:
- Moving relevant question from #1 here - which library do we want to use for parsing? `megaparsec` and `alex`+`happy` …
-
Hi !
Is it possible to add the `chainl`, `chainl1`, `chainr`, `chainr1` combinators ? Although `Control.Monad.Combinators.Expr` does exists, it feels overkill to use when there's only one layer to …
-
Example: https://hackage.haskell.org/package/bytestring-0.11.1.0/docs/src/Data.ByteString.Lazy.Internal.html#eq
![image](https://user-images.githubusercontent.com/3664523/123955801-52197580-d9aa-11…
-
I'm trying to migrate a megaparsec parser to flatparse, but it uses case-insensitive keywords. It would be really convenient to have case-insensitive versions of `string`, `char`, and `switch`. `cha…
-
Chumsky currently supports a primitive debugging system, allowing parsers to print to `stdout` when entered during a call to `Parser::parse_recovery_verbose`. Expanding this further will require some …
-
Entangled should work fine on Windows and MacOS, but I have no access to Windows or Mac systems. Information on packaging for those platforms should be included in the `packaging` directory. Possibly …
-
`WithError` is solid, but sometimes branches are missed and lead to very ugly errors. Furthermore, due to the intricacies of `Maybe`, we can get some very weird errors - which of the parts of the pars…
-
I noticed that the documentation for megaparsec says that [`getSourcePos` "is *not cheap*, do not call it e.g. on matching of every token, that's a bad idea"](https://hackage.haskell.org/package/megap…
-
Right now, parse errors include only the line number. For example:
```
Calc.ly:40: Parse error
```
It would be helpful to include a bit more easily accessible info:
* the token on which p…
-
After upgrading to GHC-9.4.5, we've been noticing a lot more of the `-package ... is hidden` errors in HLS with a stack multi-cradle.
Initially I thought this was merely #366. But after further t…