Re: [boost] Namespace for a Boost Hashing Library

I initially used boost::hash, forgetting that the unordered containers have already claimed that name. A number of alternatives have been proposed, so I hoped to get some thoughts from the wider community.

The intention for the library is to provide concepts and some implementations for checksums (like CRC32), plain hash functions (for hash tables), and cryptographic hash functions (like MD5 or SHA-256).

It seems like these are all natural allies to the stuff already in boost::hash, what's the issue in also using that name and extending the existing hash function library? Just my 2c worth, John.