Guidelines for using with WriterT about bytestring HOT 2 CLOSED

The differences between the different types of Writer monads are generally not too relevant to bytestring.

As far as the performance characteristics of the various bytestring types goes:

• Concatenating many StrictByteStrings or ShortByteStrings with (<>) via any sort of writer monad is likely to be very inefficient except in niche situations.
• Concatenating LazyByteStrings with (<>) can be efficient as long as the calls are generally right-associative. But if the individual LazyByteStrings are short, the result may have a small average chunk size, which may or may not be a problem depending on how that LazyByteString is used.
  • The codensity transform (or adding a ContT layer) can re-associate the monadic binds, if you have many nested calls that would tend to produce inefficient left-associative (<>) calls with a basic writer monad.
• Concatenating Builders with (<>) is almost always at least reasonably efficient.

from bytestring.

Thanks, I'm working on a biparsing package and I have not yet, if even possible, implemented printing a differing type than the type being parsed. I'll try to figure out how to allow parsing strict or lazy ByteString and printing Builder.

Thank you for the insight.

from bytestring.