Hi, any idea why this function requires `return` ...

# getting-started

[Alpesh Vas]

Hi, any idea why this function requires return statement in the end even if we are throwing exception onFailure

fun<T> withRetryOnRateLimit(numOfRetries: Int = 10, func: () -> T): T {
    repeat(numOfRetries) {
        runCatching(func)
                .onSuccess { return it }
                .onFailure { throw it }
    }
}

[Simon Kågedal Reimer]

The throwing happens inside a callback block. You still need to return a T in the withRetryOnRateLimit method itself, as you are declaring that.

[StavFX]

The compiler doesn’t know that it is guaranteed that either onSuccess or onFailure will get called (all it knows is that each will be called at most once).
Which also makes me wonder what’s the point of the loop here? The first iteration is guaranteed to also be the last.

[StavFX]

Also, I’m assuming that this is a simplified version of the code, because in its current form, it’s functionally identical to return func()