I have spent a good chunk of the past week tracing code, trying to
solve this problem. I'm seeing an error when using Enumerator and
Attoparsec that I can't explain. This is a reduced form of the
problem.
In general, I've observed that debugging broken iterators and
enumerators is very hard. We
I swear attoparsec-enumerator is going to give me grey hair; the error
you're receiving is because iterParser itself is divergent. Fixed in
0.2.0.3, with my sincere apologies.
On Sun, Dec 5, 2010 at 09:14, Crutcher Dunnavant crutc...@gmail.com wrote:
I have spent a good chunk of the past week
Oh thank you!
I can't believe the number of times I read through that code without
seeing that.
On Sun, Dec 5, 2010 at 12:49 PM, John Millikin jmilli...@gmail.com wrote:
I swear attoparsec-enumerator is going to give me grey hair; the error
you're receiving is because iterParser itself is
On Sun, Dec 5, 2010 at 6:14 PM, Crutcher Dunnavant crutc...@gmail.com wrote:
In general, I've observed that debugging broken iterators and
enumerators is very hard. We probably want some tooling around that;
I'm looking at an identity enumeratee with debug.trace shoved in, or
something like
