Hi all, is it a bug that suspendability on a recei...

# coroutines

[uli]

Hi all,
is it a bug that suspendability on a receiver lambda has to be explicitly declared?
If I have

private suspend fun <T> (suspend () -> T).foo()

and

private suspend fun <T> bar(lambda: suspend () -> T)

I need to explicitly write suspend { delay(1) }.foo() but it’s fine to just call bar { delay(1) } without suspend keyword

[uli]

Just in case this is considered a feature, then the bug is in Android Studio’s Refactor->ChangeSignature which does not add the `supsend`keyword to the call site when refactoring from bar to foo

[uli]

just realized, it’s not the suspend keword. It’s an inline function just to help the compiler

[Dominaezzz]

It's a little odd that the IDE makes it look like a keyword.

[uli]

It doesn't. I just did not pay attention 😃