reassign ghc

After some further debug, I found this is, in fact, a ghc bug and it was
fixed in version 8.0.2, as showed in:

https://ghc.haskell.org/trac/ghc/ticket/12621

Reply via email to