bfrk

The same happens with `where`: ```haskell test x = y where -- y is doing many important things y = 0 ``` ```haskell test x = y -- y is...

@timbertson wrote: > While I'm at it, my initial assumption was that `to-directory-tree` would take a map, instead of a record literal. That seems like it could be more flexible...

Yup. Also known as https://prelude.dhall-lang.org/Map/Type

@Bodigrim I agree that adding lots of options for customizing the output format is probably not a good idea for the reasons you stated. But this is only a problem...

Yes, good idea. There is https://hackage.haskell.org/package/terminal-size I have made a contribution to that recently ;-) in order to better support non-native Windows terminals. In fact, `isJust size` is, to the...

Actually, the ultimate solution may be to always use the full terminal width. For users who like a very wide terminal we could connect the test name and the result...

I am not sure I understand what you mean with "conservative". If you mean "keep it as is" then there is no point to this discussion, so I assume you...

Lack of progress reporting (especially for QC tests) is one of the reasons why we haven't made the transition from test-framework to tasty yet. So I am interested to see...

Instead of trying to be (too) clever and adapt the color scheme depending on the terminal's background color, why not simply make the color scheme configurable by the user? My...

I have made a PR in order to show that customization via environment variables is a viable solution. * Parse: simple, uses the Read instance for the three ConsoleFormat ingredients...