What are the nuances of using the Nothing type in generics?

The Nothing type in Kotlin is a special type that has no values and is used to denote functions that never return a result (for example, they throw an exception or run infinitely).

In the context of generics, Nothing plays an important role:

• Used as a lower bound of a type — Nothing is a subtype of all types, so it can be used to indicate that a type parameter cannot have values.
• Allows expressing the absence of a value — for example, List<Nothing> is a list that cannot contain any elements.
• Used for safely indicating the absence of a type in covariant positions.

Example of usage in generics:

fun <T> fail(): T {
    throw RuntimeException("Failure")
}

val x: String = fail() // The compiler understands that fail() returns Nothing, which is a subtype of String

Or in collections:

val emptyList: List<Nothing> = listOf()

Thus, Nothing helps the compiler understand that there will be no values in certain places, and allows safe handling of such cases in generics.