Why can't .b mean X.b when .b is an enum case with an associated value?

[vitamin (Jon Gilbert)]

@jrose

I don't actually see anything technically wrong with adding such a rule! But it would have to go through the usual language evolution process.

Thank you Jordan. If you want to check it out, I added a Swift evolution proposal here: [Pitch] Implicit member expressions for function-typed parameters with draft PR here: [Sema] Implicit member syntax through function types by gistya · Pull Request #90295 · swiftlang/swift · GitHub

So far the PR seems to work locally, would appreciate any input you might have on the risk factors mentioned in the pitch in light of the implementation. (if you have time of course)