Leon P Smith

@chrisdone, if the packages you want to use only use the public interface, the only thing you would need to do is (possibly) bump the upper bounds. If they touch...

Although, perhaps I should tweak the documentation a bit to clarify the issue that `Blaze.Builder` and `BS.Builder` are exactly the same type.

Well, snap is a bit more involved, but it still shouldn't be a serious issue. I wrote up a [more detailed blog post](http://blog.melding-monads.com/2015/02/12/announcing-blaze-builder-0-4/) regarding this new release.

Well, you can implement this without resorting to anything in the `Internal` modules: ~~~ subparser :: Text -> ConfigParserM a -> ConfigParserM [(Name, a)] subparser k p = do groupnames...

Maybe. One of the issues though is how to deal with e.g. defaulting. I mean, there doesn't seem to be a good way to implement the README example using `subparser`....

What about something like `mapSubgroups :: ConfigParser m => Name -> (Name -> m a) -> m [a]`? That name seems better to me, and the type seems a bit...

I wouldn't be opposed to it, but this package is still in a pretty rough state. I'm aware of some API bugs that I need to fix for 0.1 for...

If you'd like to take responsibility for configurator-ng on stackage, you have my blessing. There are several other packages of mine on stackage, but I'm not responsible for any of...

Oh, sorry for taking so long to get back to you. So just a quick response for now: Overall, I like the idea of allowing interpolation of value types other...

Yeah, that's pretty close to one of the workarounds I had in mind, though perhaps done a little bit nicer. One downside is that this particular workaround will just default...