If I have a type which conforms to LosslessStringConvertible (LSC) via a generic initialiser on StringProtocol:
struct Foo: LosslessStringConvertible {
init?<S>(_ description: S) where S: StringProtocol {}
var description: String { "" }
}
Autocomplete will show both the generic initialiser that I wrote, and the non-generic initialiser from LSC. They both get documentation from the protocol requirement, and it feels like clutter to include both of them in the list.
typesanitizer
commented
3 years ago
Attachment: Download
Additional Detail from JIRA
| | | |------------------|-----------------| |Votes | 0 | |Component/s | CodeCompletion | |Labels | Improvement | |Assignee | None | |Priority | Medium | md5: 9df225d1e3b8e4cff7e91c54c11b8888Issue Description:
If I have a type which conforms to LosslessStringConvertible (LSC) via a generic initialiser on StringProtocol:
Autocomplete will show both the generic initialiser that I wrote, and the non-generic initialiser from LSC. They both get documentation from the protocol requirement, and it feels like clutter to include both of them in the list.