[swift-dev] What do to when stdlib guidelines conflict with proposal?

Russ Bishop xenadu at gmail.com
Thu May 12 00:34:05 CDT 2016

> On May 11, 2016, at 10:18 PM, Chris Lattner <clattner at apple.com> wrote:
> As Dmitri, we specifically discussed this in the core team meeting (I brought it up :-).  The problem is that we really only want the toOpaque() method to exist on UnsafePointer<Void> and don’t have the ability to model that in the language yet.  When that ability exists, we’ll revise these APIs and many others.

Ah good old “same-type requirement makes generic parameter non-generic” :)

I see what the objection is and it makes sense to me. I’ll implement it as closely as I can to the spirit of the proposal.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-dev/attachments/20160511/66666858/attachment.html>

More information about the swift-dev mailing list