From e44b8dfb46d2b84dda1654b6ff757b99ee0dda38 Mon Sep 17 00:00:00 2001 From: Patrick Thomson Date: Wed, 4 Apr 2018 15:41:21 -0400 Subject: [PATCH] typo --- src/Data/Scientific/Exts.hs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/Data/Scientific/Exts.hs b/src/Data/Scientific/Exts.hs index 1488bda8f..9f43028f1 100644 --- a/src/Data/Scientific/Exts.hs +++ b/src/Data/Scientific/Exts.hs @@ -53,7 +53,7 @@ parser = signed (choice [hex, oct, bin, dec]) where fromIntegral <$> attempt @Integer (unpack ("0o" <> digs)) -- The case for binary literals is somewhat baroque. Despite having binary literal support, Integer's - -- Read instance does not handle binary literals. So we have to shell out to Numeric.readInt, which is + -- Read instance does not handle binary literals. So we have to shell out to Numeric.readInt, which -- is a very strange API, but works for our use case. The use of 'error' looks partial, but if Attoparsec -- and readInt do their jobs, it should never happen. bin = do