Community
Participate
Working Groups
Code review on core equals/hashCode: Resource.equals: - do the cheap checks first -- check type, then path, then workspace - possibly inling accessors Path.hashCode - chain hash values by multiplying by 37 Path.equals - test segments in reverse order -- more likely to hit conflict faster
Implemented and released. Minor slowdown in path creation time (due to pre-computatation of hashCode), but generally improved hash performance for both Path and IResource objects. The most significant change in terms of performance was to do the path equality testing in reverse segment order. This is more likely to hit different segments faster.
Fixed in v211