Multiconditional Loop in Kotlin

As we all know about loops, in Kotlin, loops are compiled down to optimized loops wherever possible. For example, if you iterate over a number range, the bytecode will be compiled down to a corresponding loop based on plain int values to avoid the overhead of object creation. Conditional loops are common to any programming language you pick. If you apply multiple conditions to a loop, it is called a multiconditional loop. A simple example of a multiconditional loop in Java is illustrated here:

The preceding code on execution will print out 5, 6, and 7. Let's see how we can use a multiconditional loop in Kotlin. We will be looking at a functional approach to the same thing in Kotlin

Example

The preceding multiconditional loop can be written in Kotlin like so:

It's nice, clean, and definitely not an eyesore.

• We used takeWhile, which returns a sequence containing the first elements satisfying the given predicate (in this case, i <data [i]).
• Though takewhile returns the first elements that satisfy the given predicate, you might be tempted to think that it will first evaluate the complete range and then pass to forEach.
• That would have been the case if we hadn't used .asSequence (). We converted the range to a Sequence<T>, and because of this, it was lazily evaluated. In short, it won't process the whole set of items with .takeWhile { ... } and will only check them one by one when .forEach { . . . }is up to process the next item.

First, we will work with an eager evaluation over Iterable<T>. This is the eager version, which evaluates the first function before moving on to the next one:

Output:

Inside takeWhile
Inside takeWhile
Inside takeWhile
Inside takewhile
Inside forEach
Inside forEach
Inside forEach

As you can see, the range was first processed with takewhile (which returned 0, 1, 2) and was then sent for processing to forEach. Now, let's see the lazy version:

Output:

Inside takewhile
Inside forEach
Inside takewhile
Inside forEach
Inside takewhile
Inside forEach
Inside takewhile

As you can see in the preceding example, takewhile is evaluated only when forEach is used to process an item. This is the nature of Sequence<T>, which performs lazily where possible.