Re: Why Does Hash Apparently Reorder Its Internal Representation And Other Associated Ponderings
- From: Hal Fulton <hal9000@xxxxxxxxxxxxxxxx>
- Date: Wed, 23 Aug 2006 09:10:09 +0900
Pedro Côrte-Real wrote:
On 8/22/06, Austin Ziegler <halostatue@xxxxxxxxx> wrote:
It would be ordered and have arbitrary key values, but it would not,
in fact, be a Hash. That's the point that some folks have tried to
make about this.
It is a Hash, since it provides it's interface and general performance
characteristics. It just supplies the new guarantee of insertion
ordering.
If you capitalize Hash (naming the Ruby class) that is arguably true.
But in the CS sense, a hash is not ordered.
A lot of people seem to want this so why not create a standard OHash?
A nice syntax like the [1=>2] one would be great as well.
I think I'll address a few more issues and then write this up as
an RCR.
If you don't see it in ten days, nag me. ;)
Cheers,
Hal
.
- References:
- Re: Why Does Hash Apparently Reorder Its Internal Representation And Other Associated Ponderings
- From: thoran
- Re: Why Does Hash Apparently Reorder Its Internal Representation And Other Associated Ponderings
- From: thoran
- Re: Why Does Hash Apparently Reorder Its Internal Representation And Other Associated Ponderings
- From: Austin Ziegler
- Re: Why Does Hash Apparently Reorder Its Internal Representation And Other Associated Ponderings
- From: Pedro Côrte-Real
- Re: Why Does Hash Apparently Reorder Its Internal Representation And Other Associated Ponderings
- Prev by Date: Re: Static typing ain't so bad, after all...
- Next by Date: Re: Why Does Hash Apparently Reorder Its Internal Representation And Other Associated Ponderings
- Previous by thread: Re: Why Does Hash Apparently Reorder Its Internal Representation And Other Associated Ponderings
- Next by thread: Re: Why Does Hash Apparently Reorder Its Internal Representation And Other Associated Ponderings
- Index(es):
Relevant Pages
|