java并发集合类设计思想-优快云博客

本文探讨了并发集合类如ConcurrentMap禁止使用null值的原因。主要在于并发环境下，无法判断map.get(key)返回null是因为键不存在还是值确实为null。这种不确定性在非并发环境中可通过map.contains(key)解决，但在并发环境中由于状态可能发生变化而变得复杂。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

为什么并发集合类不支持null

按照设计者Doug Lea自己的说法是：

The main reason that nulls aren't allowed in ConcurrentMaps (ConcurrentHashMaps, ConcurrentSkipListMaps) is that ambiguities that may be just barely tolerable in non-concurrent maps can't be accommodated. The main one is that if map.get(key) returns null, you can't detect whether the key explicitly maps to null vs the key isn't mapped. In a non-concurrent map, you can check this via map.contains(key), but in a concurrent one, the map might have changed between calls.

在ConcurrentMap中不允许null的原因是在非并发map允许的歧义性在并发环境下是不允许的。以null值来说，在并发环境下，无法分辨map.get(key)返回null是键不存在，还是值为null。在非并发环境下，可以使用map.contains(key)来分辨，但并发环境下两次调用期间map可能发生了改变。

我也赞同Doug Lea的说法：

I personally think that allowing nulls in Maps (also Sets) is an open invitation for programs to contain errors that remain undetected until they break at just the wrong time.

在集合中允许null（键/值），本质是对程序逃避检查错误直到错误爆发的一种鼓励。

转载于:https://www.cnblogs.com/redreampt/p/9408964.html