Ximin Luo
Ximin Luo
I think flint code does have to be changed actually, but so does many other projects, so I've filed a [GCC bug](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82677) even though it's not (I believe) strictly their...
I think it's a different bug and a bug in the C code, I also get the same error with clang-4.0. It should probably be in a separate issue. I...
hlint has taken the decision to move away from haskell-src-exts to using ghc-lib-parser instead, in ndmitchell/hlint#892
See [here](https://github.com/jaspervdj/stylish-haskell/issues/230#issuecomment-597182525) for a workaround
The following config file will work around this and related issues, without forcing a workaround to your main haskell source code: ~~~~ steps: - simple_align: {} - imports: {} -...
See [here](https://github.com/jaspervdj/stylish-haskell/issues/230#issuecomment-597182525) for a workaround
Just adding my voice in favour of this feature. :) Sadly #231 was closed :(
I will double-check this soon, although the current documentation only says "strict in its length" and does not mention strictness in the values.
The culprit is indeed Data.Sequence - forcing the item before using `|>` fixes the issue for me. (see the commit linked just above this comment). I can still see a...
> that the bug is in your code and not Data.Sequence. The advantage of a strict sequence module is that it makes such bugs less likely to occur I don't...