<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Out of curiosity, how are your other string types different from Swift String?<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 19, 2017, at 3:34 PM, Braden Scothern via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div style="color:rgb(80,0,80);font-size:12.800000190734863px" class="">Where I work we are writing a C library for cross platform development on iOS, Android, and Ubuntu. Part of what I do with this library is wrap it in Swift. We have a string type that should conform to StringProtocol. The issue is that the StringProtocol has this statement for its documentation overview:</div><div style="color:rgb(80,0,80);font-size:12.800000190734863px" class=""><br class=""></div><div style="color:rgb(80,0,80);font-size:12.800000190734863px" class="">"Do not declare new conformances to StringProtocol. Only the String and Substring types of the standard library are valid conforming types."</div><div style="color:rgb(80,0,80);font-size:12.800000190734863px" class=""><br class=""></div></div></div></blockquote><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div style="color:rgb(80,0,80);font-size:12.800000190734863px" class="">While I don't think many people will/should conform to StringProtocol, I feel like discouraging the usage of the protocol in the rare cases is is applicable takes away a very powerful tool from the language.</div><div style="color:rgb(80,0,80);font-size:12.800000190734863px" class=""><br class=""></div><div style="color:rgb(80,0,80);font-size:12.800000190734863px" class="">Are there specific implementation details in the standard library that make it so other types cannot safely conform to StringProtocol? If not is there a compelling reason for this statement to be on the protocol?</div></div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></div></body></html>