re: Force unwrapping is not just “not Swift-like.” It’s wrong. VIEW POST


I really agreed with all the statement about the using of unwrapping optionals. but sometimes on the development it's a necessary evil, if the developer is pretty confident to justify the use of ! in an object and make sure when trying accessing the object value there will be no problem with it, I've seen a lot of usage of the ! but is not a practice I really support for me even I prefer to deal with the boiler plate or make something that deals with that using the minimal code required for that operation than deal with bugs.


Yes, I love the conversation this has inspired about what others have done to use ! as safely as you can when it is necessary. A strong bias against it is a good default, and being very mindful when you do need to use it (with supporting documentation!).

code of conduct - report abuse