I've been contact by Ayende Rahien with regard to some optimisations
he's been making. Some of these may be due to profiler artefacts, but
he's concerned about the hash code of ByteString.
The full blog post is here:
Various commenters have commented that the hash code for ByteString is
pretty bad. It's relatively easy to fix (without going to the extremes
mentioned in the blog post - I don't want to use unsafe code) but that
*would* mean losing compatibility with the hash code given by Java. I
don't personally have a problem with that - hash codes should almost
never treated as persistable - but I wanted to check with others
before making a change.
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at