There's a high likelyhood that if you have unhandled enums and uncaught exceptions after a refactoring, the code is subtly broken. In C++ -Wswitch is a valuabl

There's a high likelyhood that if you have unhandled enums and uncaught exceptions after a refactoring, the code is subtly broken. In C++ -Wswitch is a valuable tool to find the former, but there is no way to find the latter. This makes writing correct exception handling code much much harder, so having Swift's strict behaviour would be great from my perspective! It sounds to me that you want to use a few days of exploratory coding to save a few hours of design work. If this type of exploration is needed, then it could be done in another language which supports it and then when the design is in decent shape it can be ported to Swift. Swift is not detrimental to the correctness of the business logic. It offers you a bedrock at the type sustem level on which to build that.