Ensure that "true" and "false" won't go in same bucket in hash table

[d-torrance]

This doesn't completely address #3468, but it at least does when the keys of the hash table are true and false.

Before:

i2 : buckets tally {true, false}

o2 = {{}, {(false, 1), (true, 1)}, {}, {}}

o2 : List

After

i2 : buckets tally {true, false}

o2 = {{(false, 1)}, {(true, 1)}, {}, {}}

o2 : List

We also refactor the code mentioned in #3468 (comment) so it doesn't rely on the order of the elements returned by values. Edit: I removed this commit because it's already dealt with in #3469.

Edit no. 2: I adjusted the hash of false to be congruent to 2 (mod 4) instead of 0 (mod 4) so that the true bucket would go before the false bucket and the builds wouldn't fail w/o #3469.

[mahrud]

What if we treated true and false as 0/1 like in C?

[d-torrance]

Works for me!

[mahrud]

I think just wait until the other one is merged first.