Re:Advancing Memory Safety
by plorkyeran on Tuesday October 15, 2024 @04:51PM
(#41852969)
When Swift first came out there was a subset of obj-c developers who hated Swift’s take on Optional. In obj-c you can freely send messages to nil and it just returns nil. In Swift you have to explicitly mark if a value is optional and handle it being nil if so, and even though this often means adding just a single character (foo?.bar), there were people who thought that Swift was just making things more complicated for no benefit.
[ Parent
| on HN ]
There are no comments on this comment yet.