Alberto Barbati wrote:
Coming back to the hash library, I think we have only three choices:
1) use reinterpret_cast<> as I proposed, but documenting that it will produce a viable hash function only if the underlying implementation satisfy certain requirements (each specific implementation /should/ document the behaviour of reinterpret_cast anyway, so the user may able to check)
2) provide the hash function (with reintepret_cast<>) only for those platforms that we are able to check in advance that will satisfy those requirements and make any use of such function produce a static assert for all other platforms
3) do not provide a hash function for pointers at all
I don't see why we should loose sleep over this. If the implementation doesn't work (meet the requirements for a hash function) on a platform that is supported by Boost, this is a bug and should be handled as any other bug.