# Re: What does it take to make an object hashable, no really

**URL:** <https://www.ruby-forum.com/t/re-what-does-it-take-to-make-an-object-hashable-no-really/68576>\
**Category:** Ruby\
**Created:** [September 13, 2006, 6:29pm UTC](https://www.ruby-forum.com/t/re-what-does-it-take-to-make-an-object-hashable-no-really/68576 "2006-09-13T18:29:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![phrogz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/2acd7d/32.png) [@phrogz](https://www.ruby-forum.com/u/phrogz)\
**Post date:** [September 13, 2006, 6:29pm UTC](https://www.ruby-forum.com/t/re-what-does-it-take-to-make-an-object-hashable-no-really/68576/1 "2006-09-13T18:29:49Z")

</div>

From: Tim P. [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)]

> You have to use eql? if you want to get a true/false result.  
> Further, for some objects it’s easy to say if they’re equal or not, but  
> very hard to define if one is “greater than” the other or not. For  
> these, it’s easy to define #eql? but impossible to define #\<=\>