If two TimeSpec values are extremely close together (e.g. (TimeSpec {sec = 43948, nsec = 402952718}, TimeSpec {sec = 43948, nsec = 402964296})) then the timeSpecs formatter will print out a value in microseconds with " µs" as the units. This can hit this GHC bug resulting in an error message like the following:
(I've just spent way too long thinking it was some situation of only happening inside a case statement or something because that's actually where my timings were close enough to cause it to happen.)
Would it be possible to change this to just use " us" for portability?
chrisdone
commented
7 years ago
If two
TimeSpecvalues are extremely close together (e.g.(TimeSpec {sec = 43948, nsec = 402952718}, TimeSpec {sec = 43948, nsec = 402964296})) then thetimeSpecsformatter will print out a value in microseconds with" µs"as the units. This can hit this GHC bug resulting in an error message like the following:(I've just spent way too long thinking it was some situation of only happening inside a case statement or something because that's actually where my timings were close enough to cause it to happen.)
Would it be possible to change this to just use
" us"for portability?