You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2023. It is now read-only.
a concatMap approach will have quite a different profile, in term of memory usage and cpu usage. Also note that this is the same approach taken in base16-bytestring for performance reasons.
@vincenthz I'm not suggesting to literally use concatMap, I'm rather asking whether you think that bytestring could provide a concatMap-like function which allows you to write toHex in a safe way (i.e. only providing a Char -> ByteString or Char -> Storable something function) with the same performance characteristics.
We were just looking at
toHex
and wondering whether it's necessary to write such a low-levelconcatMap
.Couldn't
bytestring
provide an inlinable combinator with which this could be expressed in a completely memory-safe fashion?@vincenthz Have you had tries in the past to do this?
The text was updated successfully, but these errors were encountered: