How do you handle exceptions in cold streams produced by Kotlin Flows? Be puzzled no more: <https://...

# feed

[elizarov]

How do you handle exceptions in cold streams produced by Kotlin Flows? Be puzzled no more: https://medium.com/@elizarov/exceptions-in-kotlin-flows-b59643c940fb

[zsmb]

@elizarov Really interesting read, your blog is quickly becoming the de facto coroutine documentation.

FYI, there is a small typo in there: collect { value -> pdateUI(value) }

[elizarov]

Thanks. I really hope it is not replacing documentation. We are trying to be quite thorough in the docs.

[dave08]

I'm wondering if it would be better to have catch<IOException> { ... } if someone needs to catch a specific exception instead of having to catch and rethrow the rest?

[elizarov]

Unfortunately, we’ll have to give it another name, or “catch everything” will have to be written catch<Throwable>. We might improve this part of the language in the future, though.

[Antanas A.]

Maybe could be implemented "Generic parameter defaults" as in typescript:
https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-3.html#generic-parameter-defaults

class A<T = Throwable> { ... }

[Antanas A.]

discussion: https://github.com/microsoft/TypeScript/issues/2175

[elizarov]

https://youtrack.jetbrains.com/issue/KT-1215