Hoogle Search
Within LTS Haskell 24.43 (ghc-9.10.3)
Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.
toLazyByteString :: Stringable a => a -> ByteStringstringable Data.Stringable No documentation available.
-
Unix/Posix-specific functions for ByteStrings. Unix/Posix-specific functions for ByteStrings. Provides ByteString file-descriptor based I/O API, designed loosely after the String file-descriptor based I/O API in System.Posix.IO. The functions here wrap standard C implementations of the functions specified by the ISO/IEC 9945-1:1990 (``POSIX.1'') and X/Open Portability Guide Issue 4, Version 2 (``XPG4.2'') specifications. Note that this package doesn't require the unix package as a dependency. But you'll need it in order to get your hands on an Fd, so we're not offering a complete replacement.
touchByteString :: ByteString -> IO ()unix-bytestring System.Posix.Types.Iovec Keep the ByteString alive. See unsafeByteString2CIovec.
unsafeByteString2CIovec :: ByteString -> CIovecunix-bytestring System.Posix.Types.Iovec O(1) construction Convert a ByteString into an CIovec. This function is unsafe in two ways:
- After calling this function the CIovec shares the underlying byte buffer with the original ByteString. Thus, modifying the CIovec either in C or using poke will cause the contents of the ByteString to change, breaking referential transparency. Other ByteStrings created by sharing (such as those produced via take or drop) will also reflect these changes.
- Also, even though the CIovec shares the underlying byte buffer, it does so in a way that will not keep the original ByteString alive with respect to garbage collection. Thus, the byte buffer could be collected out from under the CIovec. To prevent this, you must use touchByteString after the last point where the CIovec is needed.
putByteString :: MonadIO m => ByteString -> m ()verset Verset No documentation available.
putLByteString :: MonadIO m => ByteString -> m ()verset Verset No documentation available.