=a;D      Safe-Inferred+eIndicates format name and failed field and gives an error message. This should probably just be an h, as the calling program is really responsible for passing something formattable to the show routines.BIndicates format name, line and column and gives an error message.4Formatting information for a particular SSV variant."Characters regarded as whitespace. End of row. Field separator. #Escape character outside of quotes. :Strip "extraneous" whitespace next to separators on input.  Quote format.HFormatting information for quoted strings for a particular SSV variant.( for CSV data. Closely follows RFC 4180.W for UNIX "password file" data, i.e. colon-separated fields with no escape convention.Convert CR / LF sequences on input to LF (NL). Also convert other CRs to LF. This is probably the right way to handle CSV data.GConvert LF (NL) sequences on input to CR LF. Leaves | other CRs alone.Read using an arbitrary !. The input is not cleaned with >; if you want this, do it yourself. The standard SSV formats  and  are provided. Convert a  N representing a CSV file into a properly-parsed list of rows, each a list of  [ fields. Adheres to the spirit and (mostly) to the letter of RFC 4180, which defines the  `text/csv` MIME type. is used on the input string to clean up the various line endings that might appear. Note that this may result in irreversible, undesired manglings of CRs and LFs.MFields are expected to be separated by commas. Per RFC 4180, fields may be double-quoted: only whitespace, which is discarded, may appear outside the double-quotes of a quoted field. For unquoted fields, whitespace to the left of the field is discarded, but whitespace to the right is retained; this is convenient for the parser, and probably corresponds to the typical intent of CSV authors. Whitespace on both sides of a quoted field is discarded. If a double-quoted fields contains two double-quotes in a row, these are treated as an escaped encoding of a single double-quote.cThe final line of the input may end with a line terminator, which will be ignored, or without one.Show using an arbitrary . The standard SSV formats  and _ are provided. Some effort is made to "intelligently" quote the fields; in the worst case an  will be thrown to indicate that a field had characters that could not be quoted. Spaces or tabs in input fields only causes quoting if they are adjacent to a separator, and then only if   is !.'Convert a list of rows, each a list of   fields, to a single  g CSV representation. Adheres to the spirit and (mostly) to the letter of RFC 4180, which defines the  `text/csv` MIME type.,Newline will be used as the end-of-line character, and no discardable whitespace will appear in fields. Fields that need to be quoted because they contain a special character or line terminator will be quoted; all other fields will be left unquoted. The final row of CSV will end with a newline.RPut a representation of the given SSV input out on a file handle using the given . Uses CRLF as the line terminator character, as recommended by RFC 4180 for CSV. Otherwise, this function behaves as writing the output of  to the "J; if you want native line terminators, this latter method works for that.Perform  with .lWrite an SSV representation of the given input into a new file located at the given path, using the given  . As with ,, CRLF will be used as the line terminator.Perform  with .% #$%&'(   #$%&'()       !"#$%&'()*+,-ssv-0.3Text.SSVSSVShowExceptionSSVReadExceptionSSVEOFException SSVFormat ssvFormatNamessvFormatTerminatorssvFormatSeparatorssvFormatEscapessvFormatStripWhitessvFormatQuotessvFormatWhiteCharsSSVFormatQuotessvFormatQuoteEscapessvFormatQuoteLeftssvFormatQuoteRight csvFormat pwfFormattoNLfromNLreadSSVreadCSVshowSSVshowCSVhPutSSVhPutCSV writeSSVFile writeCSVFilebaseGHC.ErrerrorGHC.BaseStringghc-prim GHC.TypesTrueGHC.IO.Handle.TypesHandlethrowREthrowSE$fExceptionSSVShowException$fExceptionSSVReadException$fShowSSVShowException$fShowSSVReadException