It's not, as far as I'm aware, working on master.<br><br>In any case, though, Box(T()) would be just as ergonomic as Box<T>() in Swift, which I don't think is the case in Rust, and the former is already possible without the need for conditional conformances.<br><br><div class="gmail_quote"><div dir="ltr">On Tue, Jan 3, 2017 at 16:57 David Sweeris via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="gmail_msg">
> On Jan 3, 2017, at 11:31 AM, Alexis via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
> All in all, I don’t really have an opinion on whether Default makes sense for Swift. Haven’t thought about it all that much. Swift is still missing the features that make case 1 and 2 even viable motivations (conditional conformance and derive annotations), and I believe already mandates default initializers in several of the cases where 3 is relevant.<br class="gmail_msg">
I *think* conditional conformance has already been accepted and just hasn’t been implemented yet, at least not in an official “can use to publish to app store” toolchain release.<br class="gmail_msg">
<br class="gmail_msg">
- Dave Sweeris<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div>