• A value is associated with case .success can be an anything ( depends on you.)
• A value is associated with case .failure must be a type that adopts the Error protocol.

Why? Result type — It provides a clearer and type-safe way to handle the errors.

For example — Let’s create a simple function toInteger which convert a string to an integer & returns Result<Int, AnErrorType>. Please note that here case .success has an associated value of Int type & case .failure has an associated value of AnErrorType type which adopts the Error protocol.

Now we can use it like that:

So by using the Result type, it’s very clear that we’re getting back either result value of Int type or a strongly typed error value of type AnErrorType . It’s not possible to get all or none means Result type provides a more clearer and type-safe way to handle the errors.

Additionally, Result type supports a specific initializer that accepts a throwing closure —

For example —

That’s all for now. Thank you for reading! This is my first ever medium post. I hope this quick read gave you a brief insight into the world of new Result type introduction in the swift 5.0 leveraging the power of enum.

I would really appreciate any constructive criticism which comes my way, please feel free to drop your thoughts here. Please help me spread the word by liking and sharing this post with Swift lovers around the world.

And stay tuned for more glimpses into the world of Swift.