ah, that is a weird combination, and since the consistentHashKey is not defined by the user here I'm not sure it is meaningful. I think we should reject that combination.

It could possibly make sense if the `msg` itself is a `ConsistentHashable` and we could delegate `def consistentHashKey` to `msg.consistentHashKey`