Top all-time · #20094
Alexandros Salazar
Personal blog · nomothetis.svbtle.comprogrammingweb
Alexandros Salazar's personal blog at nomothetis.svbtle.com covers programming and web. Since 2014, 3 different Hacker News readers have linked it 11 times. The last post was in 2015, but the archive is still widely read.
Too few sampled comments (2) to say how often HN recommends it.?
Why HN links it
HN readers link this blog for deep dives into Swift language behaviour, such as how protocol default implementations interact with dynamic dispatch. Commenters cite its posts as a source on the subject.
Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Alexandros Salazar | One-man melting pot. Software developer. Thinker.
Most-linked posts?
- /the-ghost-of-swift-bugs-future2 people · 2 mentions · first linked 2018-08-05
What Hacker News says?
This is an interesting demonstration of a hard edge of the language. It's not because Swift holds some sort of grudge against dynamic dispatch, but rather because it's trying to reconcile some subtly incompatible design goals: 1. Adding a default implementation for a protocol requirement shouldn't stop existing types that correctly conform to that protocol from compiling. This is a reasonable user expectation and ma…
Comment linking /the-ghost-of-swift-bugs-future
on “Swift: When Unused Code Is a Bug”Submitted Smashing Swift as a story · 281 points
HN discussionThere are some rules around this, as noted in https://nomothetis.svbtle.com/the-ghost-of-swift-bugs-future : IF the inferred type of a variable is the protocol: AND the method is defined in the original protocol THEN the runtime type’s implementation is called, irrespective of whether there is a default implementation in the extension. AND the method is not defined in the original protocol, THEN the default implemen…
Comment linking /the-ghost-of-swift-bugs-future
on “Swift: When Unused Code Is a Bug”Submitted Optionals? If We Must as a story · 5 points
HN discussionSubmitted Immutable Swift as a story · 5 points
HN discussionSubmitted Type Variance in Swift as a story · 4 points
HN discussionSubmitted Error Handling in Swift: Might and Magic as a story · 4 points
HN discussionSubmitted Types as Units as a story · 3 points
HN discussionSubmitted Error Handling in Swift: Might and Magic–Part II as a story · 3 points
HN discussionSubmitted An Introduction to ReactiveCocoa as a story · 1 points
HN discussionSubmitted Understanding Optional Chaining as a story · 1 points
HN discussion