只是补充一点迈尔斯的回答中没有提到的。

如果我知道我想要第一项，我就可以 使用set.iterator().next()，但是 不然的话，我只好放弃了 数组中检索项 具体指标? 合适的方式是什么 从集合中检索数据?(其他 而不是使用迭代器)

您还应该熟悉SortedSet接口(其最常见的实现是TreeSet)。

SortedSet是一个集合(即元素是唯一的)，它通过元素的自然顺序或使用一些比较器保持有序。可以使用first()和last()方法轻松访问第一个和最后一个项。SortedSet每隔一段时间就会派上用场，当您需要保持集合无重复且以某种方式有序时。

编辑:如果你需要一个Set，它的元素按照插入顺序保存(很像List)，看一下LinkedHashSet。

根据Set集合的定义，Set中的元素是无序的。所以它们不能被索引访问。

但是为什么我们没有一个get(object)方法，不是通过提供索引作为参数，而是提供一个与我们正在寻找的对象相等的对象? 通过这种方式，我们可以访问Set中元素的数据，只需要知道equal方法使用的属性。

这是因为Set只保证惟一性，而没有说明最佳访问或使用模式。也就是说，一个Set可以是一个List或者Map，每一个都有非常不同的检索特征。

要获取Set中的元素，我使用以下命令:

public T getElement(Set<T> set, T element) {
T result = null;
if (set instanceof TreeSet<?>) {
    T floor = ((TreeSet<T>) set).floor(element);
    if (floor != null && floor.equals(element))
    result = floor;
} else {
    boolean found = false;
    for (Iterator<T> it = set.iterator(); !found && it.hasNext();) {
    if (true) {
        T current = it.next();
        if (current.equals(element)) {
        result = current;
        found = true;
        }
    }
    }
}
return result;
}

如果您不介意要排序的集合，那么您可能有兴趣看看索引树映射项目。

增强的TreeSet/TreeMap提供了通过索引访问元素或获取元素索引的功能。实现基于更新RB树中的节点权重。所以这里没有迭代，也没有列表备份。

我不确定是否有人这么说过，但你需要明白以下几点:

集合中没有“first”元素。

因为，正如其他人所说，集合没有顺序。集合是一个数学概念，特别不包括排序。

Of course, your computer can't really keep a list of stuff that's not ordered in memory. It has to have some ordering. Internally it's an array or a linked list or something. But you don't really know what it is, and it doesn't really have a first element; the element that comes out "first" comes out that way by chance, and might not be first next time. Even if you took steps to "guarantee" a particular first element, it's still coming out by chance, because you just happened to get it right for one particular implementation of a Set; a different implementation might not work that way with what you did. And, in fact, you may not know the implementation you're using as well as you think you do.

People run into this ALL. THE. TIME. with RDBMS systems and don't understand. An RDBMS query returns a set of records. This is the same type of set from mathematics: an unordered collection of items, only in this case the items are records. An RDBMS query result has no guaranteed order at all unless you use the ORDER BY clause, but all the time people assume it does and then trip themselves up some day when the shape of their data or code changes slightly and triggers the query optimizer to work a different way and suddenly the results don't come out in the order they expect. These are typically the people who didn't pay attention in database class (or when reading the documentation or tutorials) when it was explained to them, up front, that query results do not have a guaranteed ordering.