Re:Why Swift Guard Should Be Avoided
by SideburnsOfDoom on Saturday January 02, 2016 @07:47AM
(#10826032)
> If an article starts with basically "Because Uncle Bob said so", cum grano salis doesn't even cover my mindset
Uncle Bob is a recognised expert in the area. So no, his opinions on SRP should not just be dismissed out of hand.
Function size has been a pretty peculiar fetish. Even when viewed on the mythological 80x24 remote terminal, the initial function doesn't seem to be that hard to understand, and spreading it out between some function with lackluster naming doesn't really improve it all that much ("Computer science has two hard problems: cache invalidation, naming things and off by one errors").
Literate programming or the rather esoteric "refinements" at least had the advantage of being able to use proper sentences to describe the functional component and with the former you even had the option of being able to look at the code in both forms.
Having said that: As I'm not a Swift programmer (ba-doom-tish), is this all the language has that approaches Design By Contract?