That makes sense. 'sort' to the rescue!
On Tuesday, June 18, 2013, Carl Eastlund wrote:
> On Tue, Jun 18, 2013 at 3:21 PM, Dan Liebgold
> <dan.liebg...@gmail.com<javascript:_e({}, 'cvml', 'dan.liebg...@gmail.com');>
> > wrote:
>
>> According to the docs, hash->list returns a list in an unspecified order.
>> Can anyone tell me a little about how hash->list might return two
>> different orders give the same hash table? Possibly across different
>> invocations of Racket?
>>
>> Thanks,
>> --
>> Dan Liebgold [dan.liebg...@gmail.com <javascript:_e({}, 'cvml',
>> 'dan.liebg...@gmail.com');>]
>>
>
> Different invocations of Racket could do it; for instance, eq-hash-code
> assigns hash codes sequentially to objects on demand, so if objects were
> hashed in a different order nondeterministically, they would be put in a
> table in a different order. Adding or removing elements via mutation might
> also cause a table to be resized, and that might shuffle around the
> existing/remaining elements and cause them to be in a different order.
>
> --Carl
>
--
Dan Liebgold [dan.liebg...@gmail.com]
_________________________
Racket Developers list:
http://lists.racket-lang.org/dev
