isomorphism-class 0.1.0.7 → 0.1.0.8

raw patch · 2 files changed

+5/−5 lines, 2 filesPVP ok

version bump matches the API change (PVP)

API changes (from Hackage documentation)

Files

• isomorphism-class.cabal +1/−1
• library/IsomorphismClass.hs +4/−4

@@ -1,7 +1,7 @@ cabal-version: 3.0  name: isomorphism-class-version: 0.1.0.7+version: 0.1.0.8 synopsis: Isomorphism typeclass solving the conversion problem homepage: https://github.com/nikita-volkov/isomorphism-class bug-reports: https://github.com/nikita-volkov/isomorphism-class/issues

@@ -5,9 +5,9 @@ -- -- Have you ever looked for a @toString@ function? How often do you -- import @Data.Text.Lazy@ only to call its 'Data.Text.Lazy.fromStrict'? How--- about importing @Data.Text@ only to to call its 'Data.Text.unpack'? How+-- about importing @Data.Text@ only to call its 'Data.Text.unpack'? How -- about going thru the always fun sequence of--- importing @Data.ByteString.Builder@ only to to call its+-- importing @Data.ByteString.Builder@ only to call its -- 'Data.ByteString.Builder.toLazyByteString' and then importing -- @Data.ByteString.Lazy@ only to call its 'Data.ByteString.Lazy.toStrict'? --@@ -92,8 +92,8 @@     -- = Why no instance for Text/ByteString?     --     -- It is not a total isomorphism. Yes, you can represent every Text value using ByteString.-    -- However, not every ByteString can be decoded as valid Text. It doesn't matter which encoding you apply whatever encoding you apply.-    -- So it doesn't matter whether it's UTF8 or ISO-8859, or any other.+    -- However, not every ByteString can be decoded as valid Text.+    -- It doesn't matter which encoding you apply: UTF8, ISO-8859 or any other.     --     -- = String/Text is not exactly a valid isomorphism     --