Mark Karpov

@tulcod, FYI this is fixed in Megaparsec. See [here](https://github.com/mrkkrp/megaparsec/issues/6#issuecomment-131633528) how it works. The examples (and upcoming tests) include `notFollowedBy . notFollowedBy = lookAhead` property and `notFollowedBy eof` works just like...

@albertnetymk, I would consider it a bug. All lexemes are expected to consume trailing, but not leading whitespace. In this case, in some circumstances `integer` won't fail when it should,...

@albertnetymk, yes, of course. I meant that I would do it at the same time, but not in the same PR.

@aslatter, great. Should we add new test for this bug or it's not necessary? What do you think?

I think the best way to fix this is by rewriting of `sign` parser so it consumes only `+` or `-`, but fails when they are not present. This sounds...

@albertnetymk, oh indeed. I just paid more attention to tests that demonstrate the flaw, I should have noticed your solution. Anyway I'm done with it, but I'm waiting decision on...

This parser gets stuck at the end of input iterating endlessly, that's why it never returns. Follow the second version in your mind step by step and you will see...

PRs are welcome! You can extend the `VorbisField` data type and add a data constructor for "custom" fields. Also `MetaType VorbisComment` can be changed from `Maybe Text` to `[Text]` to...

> That would break the API interface though. Are you okay with that? We can bump the major version. For reading maps, maybe a new alternative `MetaType` can be defined...

@Chobbes, take a look at @minad 's solution from #41, this is one option. But as he points out this is not enough to elegantly parse languages where indentation matters....