It's definitely hashable. Here's a minimal failing test case:
https://gist.github.com/gregorycollins/5748445
On Sat, May 18, 2013 at 11:38 PM, Roman Cheplyaka wrote:
> Indeed it looks like a bug in hashable — it goes away with
> hashable-1.1.2.5.
>
> Building with -f-sse2 results in a linker er
Indeed it looks like a bug in hashable — it goes away with hashable-1.1.2.5.
Building with -f-sse2 results in a linker error
Loading package hashable-1.2.0.7 ... linking ... ghc:
/home/feuerbach/tmp/aeson/.cabal-sandbox/lib/i386-linux-ghc-7.6.3/hashable-1.2.0.7/libHShashable-1.2.0.7.a:
unknown
$ uname -a
Linux clark-laptop 3.9.0-2-ARCH #1 SMP PREEMPT Tue Apr 30 09:48:29 CEST
2013 x86_64 GNU/Linux
It'd take too long for my helpfulness to build with cabal install -fsse2
hashable and rebuild an environment.
If someone writes a bash script to do it (using cabal-dev please!), I'd be
more th
First off, everyone reporting results to this thread: your bug report would
be much more helpful if you included your OS/architecture/GHC version
combo, as well as the results of re-running the tests if you build
"hashable" with "cabal install -f-sse2".
I have a funny feeling that this is a bug in
CNR with aeson 0.6.1.0 and ghc 7.6.3.
pkg-list output can be found at http://pastebin.com/Zuuujcaz
On Saturday, May 18, 2013, Niklas Hambüchen wrote:
> Can't reproduce:
>
> % ./aeson | sort | uniq -c
>2000 Right ()
> % ./aeson | sort | uniq -c
>2000 Right ()
> % ./aeson | sort | uniq -c
Can't reproduce:
% ./aeson | sort | uniq -c
2000 Right ()
% ./aeson | sort | uniq -c
2000 Right ()
% ./aeson | sort | uniq -c
2000 Right ()
% ./aeson | sort | uniq -c
2000 Right ()
% ./aeson | sort | uniq -c
2000 Right ()
Time 100:
% ./aeson | sort | uniq -c
20 Right ()
My
My result: 2000 lines of "Right ()"
ghc-pkg list aeson says "aeson-0.6.1.0"
On May 18, 2013, at 8:25 PM, Roman Cheplyaka wrote:
> I am observing a non-deterministic behaviour of aeson's parser.
>
> I'm writing here in addition to filing a bug report [1] to draw
> attention to this (pretty sca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/05/13 17:25, Roman Cheplyaka wrote:
> I am observing a non-deterministic behaviour of aeson's parser.
>
> I'm writing here in addition to filing a bug report [1] to draw
> attention to this (pretty scary) problem.
>
> To try to reproduce this
