Hoogle Search
Within LTS Haskell 24.0 (ghc-9.10.2)
Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.
lazyByteStringHex :: LazyByteString -> Builderbytestring Data.ByteString.Builder Encode each byte of a LazyByteString using its fixed-width hex encoding.
lazyByteStringCopy :: LazyByteString -> Builderbytestring Data.ByteString.Builder.Extra Construct a Builder that copies the LazyByteString.
lazyByteStringInsert :: LazyByteString -> Builderbytestring Data.ByteString.Builder.Extra Construct a Builder that inserts all chunks of the LazyByteString directly.
lazyByteStringThreshold :: Int -> LazyByteString -> Builderbytestring Data.ByteString.Builder.Extra Construct a Builder that uses the thresholding strategy of byteStringThreshold for each chunk of the LazyByteString.
lazyByteString :: LazyByteString -> Builderbytestring Data.ByteString.Builder.Internal Create a Builder denoting the same sequence of bytes as a lazy LazyByteString. The Builder inserts large chunks of the LazyByteString directly, but copies small ones to ensure that the generated chunks are large on average.
lazyByteStringCopy :: LazyByteString -> Builderbytestring Data.ByteString.Builder.Internal Construct a Builder that copies the LazyByteString.
lazyByteStringInsert :: LazyByteString -> Builderbytestring Data.ByteString.Builder.Internal Construct a Builder that inserts all chunks of the LazyByteString directly.
lazyByteStringThreshold :: Int -> LazyByteString -> Builderbytestring Data.ByteString.Builder.Internal Construct a Builder that uses the thresholding strategy of byteStringThreshold for each chunk of the LazyByteString.
toLazyByteString :: Builder -> LazyByteStringbytestring Data.ByteString.Builder Execute a Builder and return the generated chunks as a LazyByteString. The work is performed lazy, i.e., only when a chunk of the LazyByteString is forced.
toLazyByteStringWith :: AllocationStrategy -> LazyByteString -> Builder -> LazyByteStringbytestring Data.ByteString.Builder.Extra Heavy inlining. Execute a Builder with custom execution parameters. This function is inlined despite its heavy code-size to allow fusing with the allocation strategy. For example, the default Builder execution function toLazyByteString is defined as follows.
{-# NOINLINE toLazyByteString #-} toLazyByteString = toLazyByteStringWith (safeStrategy smallChunkSize defaultChunkSize) L.Emptywhere L.Empty is the zero-length LazyByteString. In most cases, the parameters used by toLazyByteString give good performance. A sub-performing case of toLazyByteString is executing short (<128 bytes) Builders. In this case, the allocation overhead for the first 4kb buffer and the trimming cost dominate the cost of executing the Builder. You can avoid this problem usingtoLazyByteStringWith (safeStrategy 128 smallChunkSize) L.Empty
This reduces the allocation and trimming overhead, as all generated LazyByteStrings fit into the first buffer and there is no trimming required, if more than 64 bytes and less than 128 bytes are written.