Why does hashcode() returns an integer and not lon

Question

This question already has answers here:

Why Object#hashCode() returns int instead of long (3 answers)

Closed 2 years ago.

In java, hashcode() method, returns integer instead of long. Is there any specific reason?

Answer 1

Using the hashCode is to have N buckets where the hashCode % N determines the bucket of elements, hopefully being 1 (no conflicting hashCodes).

For N, for the hash code, an int is entirely sufficient; indeed one needs to have most variety in the lower bits; having a long without using the higher bits (when N would be a power of 2), would be counter productive.

Speed of course is a requirement too: int being slightly better on the final CPU.

Answer 2

Well, one good reason is that the hashCode based data structures (HashSet, HashMap) use an array to store the bins, and arrays are limited to int indices. You will gain nothing by a long hashCode() if you must map it to an int array index.