We should be preferring the shorter one, but unfortunately our logic in this area doesn't like it when the defaulted arguments aren't at the end. The importer could choose not to default arguments that aren't at the end, but that would affect methods that aren't overloaded on import. Both of these changes would be source-breaking, too.

In this specific case, we could probably mark the first one as unavailable. @phausler, any opinion?

(Note that things are even worse than usual because the HTML is lowercased upon import, so any diagnostics you're getting are about the Swift 2 names, which are then themselves marked unavailable. But using html produces the same issue.)

This shouldn't be marked as unavailable; the compiler shouldn't make ambiguous default arguments. IMHO this looks like a duplicate of https://bugs.swift.org/browse/SR-1408

We probably can't do either of the things I suggested because it would be source-breaking, and we missed the cutoff for Swift 3.0. I'm asking if you want to do something for this particular API despite that.