Thanks for these thoughts, Dave. It’s a vexing problem. Quoting this especially for its insight:
As I mull all this over, I keep coming back to this:
That’s the crux of it for me. If we could answer “yes,” I would be a happy redhead.
(By “uniform meaning” I just mean the developer should be able to reason correctly about the answers to semantic distinctness questions: Does this method implementation newly introduce a semantically distinct behavior? Does it override an existing one? Could it be overridden?)
We aren’t ever going to make semantic distinctness questions painless, but it feels like we should be able to at least make them orthogonal to the rest of the language. More orthogonal than they are, anyway. The “Ghost of Swift Bugs Future” status quo centers around the fact that rules about semantic distinctness of a thing currently depend on what it’s nested inside in ways that seem unnecessary.