Dag Odenhall

Under the test name, possibly replacing any docstring (as the test source includes it), with syntax-highlighting. Might this be useful at all? Not really difficult to locate failing tests, at...

Write tests as reST documents. Inline diffs for failing doctests. Execute code blocks and check for exceptions. Run test documents as part of test suites and build as part of...

Consider moving "original" to .Unsafe

3

It's debatable whether it's a true law of `Eq` (opinions varied in `#haskell`), but I'd say it certainly is an expectation that if `a == b` then `f a ==...

Handle boolean attributes better

13

http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#boolean-attribute Currently attributes like `disabled` and `checked` (there are many more) in blaze-html all take an argument which means you have to give them the empty string or the name...

Use -fno-code by default

2

See https://github.com/kazu-yamamoto/ghc-mod/issues/80

Filter out errors and warnings for other files

2

I think since the `check` command is per file (not project), output for other files should be filtered out: ``` console $ hdevtools check -g-isrc src/Kibr/CLI.hs src/Kibr/State.hs:123:46: Not in scope:...

Context locals

1

Yea, I keep thinking of things that are in Werkzeug that are neat :D while I don't want to depend on the whole of Werkzeug for something non-WSGI. Would be...

Allow setting the complete -G option

2

I want to complete XML files. You can do this with bash completions via `-A file -G '*.xml'`.

Internationalization of usage help

1

I don't need this critically, but thought I'd suggest it anyway. The "obvious" way to do it seems to me to be having messages be algebraic types, probably one user-provided...

Records for configuring Remote

4

**TLDR:** Should I use separate types for client and server configuration, or unify the configuration in a shared type? I'm working on replacing the arguments to `acidServer` and `openRemoteState` with...