Picking the right way of failing in Swift
John Sundell
1825

Hi John. Thanks for the post. Great read.

How would you protect your codebase against assertionFailure() not having a return statement and breaking your release builds?

I am trying to make test-driven choices going forward. If you have enough feedback to write a post about how to make better test-driven choices, I would really appreciate it.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.