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
I'm guessing that keeping track of where an error occurs while decoding makes elm-bytes-parser slower than elm/bytes. Is there any bench-marking to determine how much slower though?
I'm working on elm-codec-bytes and I would like for it to be able to give useful error messages when it fails to decode data. I'm considering replacing elm/bytes with this package but I only want to do that if the performance difference isn't large.
The text was updated successfully, but these errors were encountered:
I'm guessing that keeping track of where an error occurs while decoding makes
elm-bytes-parser
slower thanelm/bytes
. Is there any bench-marking to determine how much slower though?I'm working on
elm-codec-bytes
and I would like for it to be able to give useful error messages when it fails to decode data. I'm considering replacingelm/bytes
with this package but I only want to do that if the performance difference isn't large.The text was updated successfully, but these errors were encountered: