LazyList | Lazy load of images in Android | Computer Vision library

Here's a basic implementation of a faro shuffle. This is an out-shuffle ("faro out, man!") just because it's a bit easier to code than an in-shuffle.

I have imported apache commons lib for my spring boot project in pom.xml.

Compilation error occurs for the below snippet only when it is method level implementation and error does not occur when it is defined in main. What is the difference ? Scala version used is 2.13.5.

After upgrading one of my projects to scala 2.13.4 I get the following error:

There is an example of a simple API that uses ZIO effect to return None or Option[String]. I use ZIO Schedule to run the effect as long the None is returned, but limited to a certain number of times. The example is based on the code from ZIO usecases_scheduling:

I'm building a Scala facade to a Clojure Channel delivering chunks of data and I want to represent it as a LazyList[Future[Either[String, Int]]] where the left side can hold an error message and the right side data. Retrieving each chunk from the Channel is a blocking operation and I therefore want to encapsulate each chunk in a Future.

Each chunk result type determines how we should proceed building the lazy list:

1. null: no more results on channel, return list
2. String: add Left(error) and return list
3. Int: add Right(data) and recurse for next chunk

My questions is wether we can build such list in a lazy and non-blocking way?

This is what I have come up with so far, but the head is evaluated (not lazy) and the Await.result blocks:

Assume that we have the following LazyList definition:

In Scala 2.13 I have encountered a problem with pattern matching using the operator #::, which displays error Cannot resolve method #::.unapply when used as follows:

I'm using Scala 2.13.1 and evaluate my examples in a worksheet.

At first, I define two functions that return the range of a to (z-1) as a stream or respectively a lazy list.