问题描述
我希望将数据存储在地图中,并且具有密钥一致性,但是我希望地图使用我的关键类的equals方法。
I want to store data in a map, with key unicity, but I would like the map to use the equals method of my key class.
HashMap不使用equals方法(我可能是错误的,如果我的测试是错误的)。
It seems that HashMap doesn't use the equals method (I may be wrong, if so my tests are wrong).
我的问题是,地图使用hashCode来检查重复,我想要一个使用equals的地图实现。
My problem here is that the map use hashCode to check for duplicate, and I would like a map implementation that use equals.
我正在密钥中存储时间戳,并希望使它能够使2个键等于如果有时间戳差异不超过定义的金额(例如1000毫秒)。
I am storing timestamp in the key, and would like to make it so that 2 keys are equals if there timestamp difference does not exceed a defined amount (let say 1000 ms).
编辑:代码
public class CleanKey
{
private DateTime start;
private DateTime end;
public int hashCode()
{
final int prime = 31;
int result = 1;
result = prime * result + ((end == null) ? 0 : end.hashCode());
result = prime * result + ((start == null) ? 0 : start.hashCode());
return result;
}
public boolean equals(Object obj)
{
if(this == obj)
return true;
if(obj == null)
return false;
if(getClass() != obj.getClass())
return false;
CleanKey other = (CleanKey) obj;
if(end == null)
{
if(other.end != null)
return false;
}
else if(Math.abs(Millis.millisBetween(end, other.end).getMillis()) > 1000)
return false;
if(start == null)
{
if(other.start != null)
return false;
}
else if(Math.abs(Millis.millisBetween(start, other.start).getMillis()) > 1000)
return false;
return true;
}
}
推荐答案
它使用等于
,但是首先使用 hashCode
。它只会打扰在具有相同哈希码的密钥上调用等于
- 这就是它如何管理效率。这不是问题,只要您的 hashCode
和等于
方法服从 java中指定的合同.lang.Object
。
It does use equals
, but it uses hashCode
first. It will only bother calling equals
on keys with the same hash code - that's how it manages to be efficient. That's not a problem so long as your hashCode
and equals
method obey the contract specified in java.lang.Object
.
你不能这样做。它违反了平等的合同,因为你不能有传递性。假设我们有三个键x,y和z具有以下时间戳:
You can't do that. It violates the contract of equals, because you can't have transitivity. Suppose we have three keys x, y, and z with the following timestamps:
x 400
y 1200
z 2000
根据您的描述, x.equals(y)
将为true, y.equals(z)
将为true,但 x.equals(z)
将是错误的,因此违反了
By your description, x.equals(y)
would be true, y.equals(z)
would be true, but x.equals(z)
would be false, thus violating the contract of Object.equals
.
- 它是反身:对于任何非空引用值x, x.equals(x)应该返回true。
- 它是对称:对于任何非空参考值x和y,x.equals(y)应该返回true当且仅当y.equals(x)返回true时。
- 它是传递:对于任何非空参考值x,y和z ,如果x.equals(y)返回true并且y.equals(z)返回true,那么x.equals(z)应该返回true。
- 它是一致:对于任何非空参考值x和y,x.equals(y)的多次调用始终返回true或始终返回false,前提是在对象的equals比较中没有使用任何信息被修改。
- 对于任何非空值参考值x,x.equals(null)应返回false。
- It is reflexive: for any non-null reference value x, x.equals(x) should return true.
- It is symmetric: for any non-null reference values x and y, x.equals(y) should return true if and only if y.equals(x) returns true.
- It is transitive: for any non-null reference values x, y, and z, if x.equals(y) returns true and y.equals(z) returns true, then x.equals(z) should return true.
- It is consistent: for any non-null reference values x and y, multiple invocations of x.equals(y) consistently return true or consistently return false, provided no information used in equals comparisons on the objects is modified.
- For any non-null reference value x, x.equals(null) should return false.
这篇关于是否存在使用equals方法进行密钥检查的映射?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!