A modern programming language that makes developers happier.

kotlinlang

<@UEJ9199JN> are you returning something out of it, or otherwise doing something that requires it to be exhaustive?

internal sealed class RemoveProjectLibraryResult {
    class Removed(val library: ProjectLibraryModel) : RemoveProjectLibraryResult()
    class NotFound(val id: ProjectId) : RemoveProjectLibraryResult()
}

also: <https://proandroiddev.com/til-when-is-when-exhaustive-31d69f630a8b>

Let me read the post and get back if I’m wrong. Thanks Zach

I was surprised that `when` is not exhaustive when it’s not used as an expression.  Ran into that some months ago.
I was under the impression it was done for safety, and that gave me warm-fuzzies.  Looks like it was only done because the compiler needs a value for the expression.

I _*believe*_ the equivalent in Swift is always exhaustive.

Thanks. That solved my issue. I was doing:
        when (createProjectLibrary(projectId)) {
            is Created -&gt; addLibraryAsset(projectId)
        }

you could even use an `if` statement if you’re only looking for a single type

Untitled

of course. I was just concern because I was not getting a compilation issue( I was only handling 1 case)

yeah, the `.exhaustive` val from that article will let you force your when blocks to be exhaustive. Outside of that, I guess there are situations where you only want to handle a couple of potential cases, so the compiler doesn’t force you ALWAYS to handle them all