fromIterable was quite old code, from a time when we believed that it was more important to provide concurrency friendliness in the case of large or infinite iterables. However, we have no evidence that anyone uses most with iterables in that way. So, the simplest thing to do is simply to plow through the iterable as quickly as possible, like we do for arrays in fromArrays.
If it turns out there is a need for a concurrency-friendly version, we can entertain the idea of adding a new API or separate package for that.
fromIterable was quite old code, from a time when we believed that it was more important to provide concurrency friendliness in the case of large or infinite iterables. However, we have no evidence that anyone uses most with iterables in that way. So, the simplest thing to do is simply to plow through the iterable as quickly as possible, like we do for arrays in fromArrays.
If it turns out there is a need for a concurrency-friendly version, we can entertain the idea of adding a new API or separate package for that.