Understood why we'd deprecate `is_a? Hash` and `kind_of? Hash` but ... it sure reads funny.

What if you're passing the object to a method that really *wants* a `Hash` and checks for it, and now gives a deprecation warning?

The cure feels like it may be worse than the disease.