From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Question for those developing on Gradle itself: does it make sense for there to be a Kotlin extension that converts something like a `Provider&lt;List&lt;String&gt;&gt;` to `Sequence&lt;String&gt;` or a `FileCollection` to a `Sequence&lt;File&gt;`? Or am I off-base in terms of the lazy semantics contained therein?

`Sequence` vs `Iterable` is mostly a distinction for the methods available on them, not in how the data is generated -- there's no benefit in adding a specific integration here vs. just calling `asSequence()` on the existing `Iterable` implementation. <https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.collections/as-sequence.html>

Well, `Provider&lt;List&lt;...&gt;&gt;` could perhaps benefit, but I don't know if it's useful enough to warrant such an extension. You also have to consider that it loses task dependency information that could be retained by staying with a `Provider`.

Yeah, my fear was that there was something unintended if I did
```val provider: Provider&lt;List&lt;String&gt;&gt;
val sequence = sequence {
  yieldAll(provider.get())
}```


That will work, and would be equivalent to any extension that could be added to Gradle. Typically a `Provider` should not be resolved before execution though, so I'm unsure how much value there is in having such a sequence. You might as well just wait to get an iterator directly from the `List` once you need it.

That is, you're just trading one lazy wrapper for another -- neither is really going to work that differently in terms of when it gets resolved.