object.d and hash_t confusion?

[kris]

James Pelcis wrote:
> Since the only non-bug problem I noticed here was a programmer error 
> (using uint instead of hash_t), why should it be changed?

Well, the hope was that such an easy-to-make 'mistake' would be caught 
by the compiler :)

> If a change does need to be made though, the alias could be changed into 
> a typedef.  That would check for the problem regardless of the platform.

Yep, but probably requires casting. Walter has noted on a number of 
ocassions that a cast is not exactly intended for general purposes. I 
just wonder if this should be considered a special-case or not