I think I got a lint issue when I use a suspend function as parameter

# coroutines

[Javier]

I think I got a lint issue when I use a suspend function as parameter

[Javier]

message has been deleted

[Javier]

message has been deleted

[Javier]

The last image solves the problem, obviously the suspend is not needed there, but if I want to use the function directly how you can see in the first image, I need the suspend, is there a workarround to avoid this?

[streetsofboston]

Yeah… any fun () -> T is not the same as fun suspend() -> T nor vice versa…..
Instead of the unused suspend of your populateTextView, do this instead:

lifecycleScope.launch {
  viewModel.users.collect {
    populateTextView(it)
  }
}

[Javier]

Yeah, I know I can do that, but I would like to use the reference

[streetsofboston]

It would be great if any fun A.(B) -> C would be assignable to a suspend fun A.(B) -> C …. but that is not the case…..

[streetsofboston]

Thing is a suspend fun A.(B) -> C translates to a fun A.(B, Continuation<C>) -> Any …. and that is not compatible with `fun A.(B) -> C`…. But it could be solved with some syntactic sugar 😄

[Javier]

Yeah, at this moment maybe is not possible directly

[Javier]

message has been deleted

[Javier]

message has been deleted

[Javier]

Maybe it can help someone

[streetsofboston]

I guess the compiler can’t deal with an overloaded definition of collect where the diff of its parameter is only a missing suspend keyword? What happens if you’d rename populate to collect?

[octylFractal]

I think this is part of https://youtrack.jetbrains.com/issue/KT-15917

[streetsofboston]

And Roman’s answer to that issue is “The design resolution is that conversion from regular functions to suspending function will be supported.”
I guess it’s in the pipeline, just not yet implemented 🤞

[Javier]

Yeah, I can't use collect

[Javier]

The problem of that answer is... 2017 But I think it is planned for 1.4. Maybe @elizarov can confirm

[elizarov]

Might come in 1.4. Not definite yet.