Pretty sure we've never supported this, just in the parser. It's a reasonable enhancement to the feature, although honestly I'm still unhappy with having this feature at all rather than something like @qualified import.

Importing .. would certainly look weird. import Foo.... Maybe you'd have to use backticks.

Ah, good to know

Is there that big of a distinction between functions and operators that `import func Module.functionName` would be supported, but not importing an operator?

No, no reason. There's a difference between operator functions and the operator decls themselves, but (IIRC) the operator decls currently leak in no matter what you do. This would only apply to the functions and so would behave pretty much exactly like the normal function case. We just don't even attempt to parse an operator following the dot.

Comment by Nikita Leonov (JIRA)

@belkadan the fact that operators disregard importing rules and leaks is really frustrating. I was not able to find a way to import just a function from a library and do not import operators. Is it subject to change in Swift 3?

It is not at the moment. Please bring it up on swift-evolution if you have an alternate model. (That's also separate from this bug.)