Immanuel,
Since a heading always starts with a new line (and ends with a colon
followed by a carriage return or just a colon?), I think it might be
useful to first separate the input into lines and then classify them
depending on whether it's a heading or not and reassemble them into the
value
seFromFile section "/tmp/test.txt"
> Right (Section (Top "top 1") (Content ""))
>
> I don't understand the behaviour of the content parser here. Why does
> it return ""? Or perhaps more generally, I don't understand the
> manyTill c
Ts). Am I missing
some library, or is my understanding correct? If it's the latter,
is there any fundamental limitation that prevents creating such a
library? Maybe there are other (but still elegant) ways to satisfy
my requirements without using GADTs?
3) 'gdiff' doesn't support polymorphic datatypes. Is there any other
library that does?
[1] http://www.serpentine.com/blog/2010/03/03/whats-in-a-parsing-library-1/
[2] http://en.wikibooks.org/wiki/Haskell/GADT
PS: My attempts so far are in
https://github.com/achudnov/language-nextgen/blob/master/Language/Nextgen/Syntax.hs
Regards,
Andrey Chudnov
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
Thanks for a prompt reply, Roman.
On 05/28/2013 04:52 PM, Roman Cheplyaka wrote:
> Any syb-style library works with GADTs, by the virtue of dealing with
> value representations instead of type representations.
I tried to use syb, but the following code fails to typecheck for me.
What am I doing w
On 08/05/2013 02:48 PM, Roman Cheplyaka wrote:
(which is unmaintained).
Has this been confirmed by the author/maintainer?
Tasty supports HUnit, SmallCheck, QuickCheck, and golden tests out of
the box (through the standard packages), but it is very extensible, so
you can write your own test pr
So is there a high-level comparison of HSpec and tasty? The only
difference I've glimpsed so far was that HSpec has a syntactic sugar for
describing tests which, honestly, I haven't found very useful.
So, could someone write up a quick comparison of the two for the benefit
of the folks like me w
Hello. What are the best practices in deprecating packages on Hackage?
I've seen packages marked "DEPRECATED" in the synopsis field on Hackage,
and one could add GHC "deprecated" pragmas for every module, but is that
the best one can do?
Thank you i
