btw, was it introduced for a specific case? Maybe coroutines related. Or just for generic purposes?

It's complicated question to be honest :)

I'd say it is good for generics.

Because it called now Result (not SuccessOrFailure as before) and in package kotlin (so doesn't require import)

@gildor do you consider that using a sealed class instead of the builtin Result useless ? because the builtin one already covers the use case?

What do you mean?

my bad, I thought the Result builtin was also a sealed class in the implementation. I just wanted to know if the use is justified if I want the Success and Error cases handled nicely

There is nothing magic in Result implementation, you can write own version using inline classes

@Mehdi answering your question, use your own class, because your case is domain specific. Also, from the Result KEEP:

NOTE: This Result class cannot be used directly as a return type of Kotlin functions. See limitations section for details.

You can use Result as return type, there is a special flag to enable it