Data.Svfactor.Print

Printing is the process of turning an Sv into a textual representation, such as a ByteString.

If you want to turn your data type into a textual representation, you should look instead at Data.Svfactor.Encode

Documentation

printSv :: Sv ByteString -> ByteString

Print an Sv to a ByteString value.

printSvLazy :: Sv ByteString -> ByteString

Print an Sv to a lazy ByteString value.

printSv' :: PrintOptions s -> Sv s -> ByteString

Converts the given Sv into a strict ByteString

printSvLazy' :: PrintOptions s -> Sv s -> ByteString

Converts the given Sv into a lazy ByteString

printSvText :: Sv Text -> ByteString

Print an Sv containing Text to a ByteString

printSvTextLazy :: Sv Text -> ByteString

Print an Sv containing Text to a ByteString

writeSvToFile :: FilePath -> Sv ByteString -> IO ()

Writes an sv to a file. This goes directly from a Builder, so it is more efficient than calling printSv or printSvLazy and writing the result to a file.

writeSvToHandle :: Handle -> Sv ByteString -> IO ()

Writes an sv to a file handle. This goes directly from a Builder, so it is more efficient than calling printSv or printSvLazy and writing the result to the handle.

writeSvToFile' :: PrintOptions s -> FilePath -> Sv s -> IO ()

Writes an sv to a file. This goes directly from a Builder, so it is more efficient than calling printSv or printSvLazy and writing the result to a file.

This version is polymorphic, but as a penalty you have to tell me how to get a Bytestring Builder.

writeSvToHandle' :: PrintOptions s -> Handle -> Sv s -> IO ()

Writes an sv to a file handle. This goes directly from a Builder, so it is more efficient than calling printSv or printSvLazy and writing the result to the handle.

This version is polymorphic, but as a penalty you have to tell me how to get a Bytestring Builder.

module Data.Svfactor.Print.Options