I prefer to put each chained method call on a separate line when writing functional code in Java. And extracting a method is a nice way to introduce a method name to summarize what's going on in an important intermediate step. Code takes up more lines, but less width, which is neither here nor there. Yes, this approach to method chain formatting may seem a bit extreme - but I find it very clean and consistent. what I guess I'm starting to settle on around formatting and indentation: Here's an example of my program running with the above input:Ġ. each first name, last name, and email is a separate token, and the values are lists of indices of entries that contain that token. You're supposed to create an inverted index, basically a Map> where the key are tokens extracted from the entries, i.e. Given a list of strings that represent entries in a phone book (one entry per line)

In the following example, we will traverse through the 'Subject' array and we will print the index along with the value.I've been working on one of the Kotlin projects at, Simple Search Engine, and the second to last stage has a bit of a challenging requirement to create an inverted index. forEachIndexed is an inline function which takes an array as an input and its index and values are separately accessible.

Nstead of using forEach() loop, you can use the forEachIndexed() loop in Kotlin. In this article, we will see how we can access the index of an array in Kotlin while using forEach loop. Sometimes it becomes necessary to access the index of an array.

Kotlin for each with index