两个评论

There is no need to convert Iterable to Collection to use foreach loop - Iterable may be used in such loop directly, there is no syntactical difference, so I hardly understand why the original question was asked at all. Suggested way to convert Iterable to Collection is unsafe (the same relates to CollectionUtils) - there is no guarantee that subsequent calls to the next() method return different object instances. Moreover, this concern is not pure theoretical. E.g. Iterable implementation used to pass values to a reduce method of Hadoop Reducer always returns the same value instance, just with different field values. So if you apply makeCollection from above (or CollectionUtils.addAll(Iterator)) you will end up with a collection with all identical elements.

只要你调用contains, containsAll, equals, hashCode, remove, retainAll, size或toArray，你就必须遍历元素。

如果您偶尔只调用isEmpty或clear等方法，我认为您最好是惰性地创建集合。例如，你可以有一个支持数组列表来存储先前迭代的元素。

我不知道任何一个库中有这样的类，但是编写它应该是一个相当简单的练习。

我经常使用fluentiatable .from(myIterable). tolist()。

有点晚了，但我创建了一个非常优雅的Java 8解决方案，允许将T的Iterable转换为T的任何集合，而不需要任何库:

public static <T, C extends Collection<T>> C toCollection(Iterable<T> iterable, Supplier<C> baseSupplier) 
{
    C collection = baseSupplier.get();
    
    iterable.forEach(collection::add);
    
    return collection;
}

使用的例子:

Iterable<String> iterable = ...;
List<String> list = toCollection(iterable, ArrayList::new);

我在试图获取项目列表时遇到了类似的情况，而不是在CrudRepository接口中声明的默认Iterable<T> findAll()。因此，在我的ProjectRepository接口(从CrudRepository扩展而来)中，我简单地声明了findAll()方法来返回一个List<Project>而不是Iterable<Project>。

package com.example.projectmanagement.dao;

import com.example.projectmanagement.entities.Project;
import org.springframework.data.repository.CrudRepository;
import java.util.List;

public interface ProjectRepository extends CrudRepository<Project, Long> {

    @Override
    List<Project> findAll();
}

我认为这是最简单的解决方案，不需要转换逻辑或使用外部库。

试试Cactoos的StickyList:

List<String> list = new StickyList<>(iterable);