From d19efff3b167122a83f5c269fd6ecb8cf9c78f33 Mon Sep 17 00:00:00 2001 From: michaelt Date: Sun, 7 Feb 2016 21:06:50 -0500 Subject: add travis --- Pipes/Prelude/Text.hs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'Pipes/Prelude') diff --git a/Pipes/Prelude/Text.hs b/Pipes/Prelude/Text.hs index ee3e104..701d5f6 100644 --- a/Pipes/Prelude/Text.hs +++ b/Pipes/Prelude/Text.hs @@ -33,7 +33,7 @@ import Prelude hiding (readFile, writeFile) @Pipes.Prelude@ and @Pipes.Safe.Prelude@ - a final \-@Ln@ being added where necessary. In using them, one is producing and consuming semantically significant individual texts, understood as lines, just as one would produce or pipe 'Int's or 'Char's or anything else. - Thus, the standard materials from @Pipes@ and @Pipes.Prelude@ and + The standard materials from @Pipes@ and @Pipes.Prelude@ and @Data.Text@ are all you need to work with them, and you can use these operations without using any of the other modules in this package. @@ -78,7 +78,7 @@ quit to see why @pipes-bytestring@ and this package, outside this module, take a different approach. Furthermore, the line-based operations, - like those in @Data.Text.IO@, use the system encoding (and @T.hGetLine@) + like those in @Data.Text.IO@, use the system encoding (and @T.hGetLine@, @T.hPutLine@ etc.) and thus are slower than the \'official\' route, which would use the very fast bytestring IO operations from @Pipes.ByteString@ and encoding and decoding functions in @Pipes.Text.Encoding@. Finally, the line-based -- cgit v1.2.3