Lev Dvorkin

> I think the best thing is probably to update the documentation - it definitely is always non-empty. Changing the type has some advantages, but is also going to break...

Upd. `v1-build` fails when trying to add extra libraries with similar errors: ``` mintty-0.1.4-AFZfdEdKJet3r0mUOoGb3u failed during the final install step. The exception was: dieVerbatim: user error (cabal-3.6.2.0.exe: 'C:\Program Files\ghcup\bin\ghc-pkg.exe' exited...

Yes I've done so and all works for me now. Thank you

@mrkkrp Yes I'd like to implement it. As I understand, it should be located in `Text.Megaparsec.Debug`. However, I'm not sure about some points: - Can we just move `dbg` in...

> More precisely, the problem seems to be that it discards the error at offset 0 completely while it potentially still can be useful later (when the error is converted...

Yes, currently, as far as I can see, only three features are supported: `::`, `->`, `=>` in *function* type signature. I've implemented replacement of `->` in GADTs in my fork,...

Thanks very much for this list! It was very helpful for me. I had a problem to find where `>-` and `>>-` are used. If you have an example, please,...

@wo Yes, from Fitting 2007 (Handbook of Modal logic, chapter 2): "A tableau branch is called closed if it contains T Z and F Z for some formula Z, or...

> Since hints are only for non-fancy errors (it is a collection of ErrorItems) there is no way the error about indentation could be persisted in this case. However, why...

This issue seems to be duplicate of #320, which is already fixed in 986cea995f0272f4db470b24bf390ffc8edaeb00