Jasper Van der Jeugt
Jasper Van der Jeugt
True. But I would advise everyone to close the tags, in order to avoid any parsing ambiguations.
I'm not sure if this issue is severe enough to be fixed. Most people who rely on whitespace usually have sort of highlighting in their editor, and so they would...
Too be honest, the only use case I can think of is having a [whitespace](https://en.wikipedia.org/wiki/Whitespace_%28programming_language%29) quasiquoter, and even that's very esoteric. I suspect that, in fact, if you are embedding...
This happens because we use `haskell-src-exts` as a library to parse the Haskell file. More info can be found in this issue: https://github.com/haskell-suite/haskell-src-exts/issues/304
Released in `v0.14.3.0`
@Mikolaj That seems like a separate issue, please create a new one -- FYI stylish-haskell is currently using GHC 9.2 as a parser (regardless of which GHC it is compiled...
Yeah, the option should probably be the default (don't reformat the field if it will cause us to violate max columns).
I'm always open to add more options. As long as they're cleanly implemented and come with tests, they shouldn't hurt maintenance too much.
There are currently no plans to add this to `stylish-haskell`. It's not impossible, but it would require a decent amount of work.
Hmm, I don't think this should be the default behaviour. Returning a non-0 exit code is appropriate if there's an error and other tools seem to be doing this as...