>The challenge with exceptions is there is zero indication at the call site that a function can throw. Swift has that. Calling a potentially throwing function

>The challenge with exceptions is there is zero indication at the call site that a function can throw. Swift has that. Calling a potentially throwing function requires that you put "try" in front of it. The downside is that you don't know what it throws (similar to Rust functions returning dyn Error)