Closed HEIGE-PCloud closed 8 months ago
Was this present in 0.2.3.0
?
No
Apparently, forcing unsigned
numbers in the definition of signed numbers does it... not entirely sure why actually, but easy fix
Ahhhh of course, order of evaluation in the Lexeme
constructor... evil
Basically, the internal Lexeme
type is fully strict, and had fields mutually defined in terms of each other (in this case, natural nonlexeme
was passed to the definition of integer
for nonlexeme
. I thought Haskell was fine with that because the record was in-construction, but it was only ok because I left that argument to the mkSigned
function lazy. I banged it during my work earlier today, and that causes an infinite loop. It's fixed now, will release 0.2.4.1
shortly.
0.2.4.1
has landed on Hackage
To reproduce, in
cabal repl