[swift-evolution] [Review] SE-0006 Apply API Guidelines to the Standard Library
jtbandes at gmail.com
Sat Jan 23 02:59:01 CST 2016
> What is your evaluation of the proposal?
I believe the Unmanaged -> UnsafeReference / OpaquePointer changes are too
large to be part of this proposal; they should be reviewed separately.
There was some discussion about this in a thread last month. Particularly,
I'm concerned that there is still a gap between UnsafePointer<Void> and
OpaquePointer APIs. I submitted a related proposal, SE-0017, which was
never scheduled for review:
I'm also a little concerned about Integer, SignedInteger, and
UnsignedInteger, which are protocols but might look like concrete integer
types to the reader. My first thought is that "Integral" would be better
for this, but it doesn't match the "noun or capability" note in the API
Otherwise, I'm generally fine with the proposed changes.
> Is the problem being addressed significant enough to warrant a change to
Yes; consistency is important.
> Does this proposal fit well with the feel and direction of Swift?
Yes, by definition.
> How much effort did you put into your review? A glance, a quick reading,
or an in-depth study?
On Fri, Jan 22, 2016 at 1:02 PM, Douglas Gregor via swift-evolution <
swift-evolution at swift.org> wrote:
> Hello Swift community,
> The review of SE-0006 "Apply API Guidelines to the Standard Library"
> begins now and runs through January 31, 2016. The proposal is available
> Reviews are an important part of the Swift evolution process. All reviews
> should be sent to the swift-evolution mailing list at
> or, if you would like to keep your feedback private, directly to the
> review manager. When replying, please try to keep the proposal link at the
> top of the message:
> Proposal link:
> Reply text
> Other replies
> goes into a review?
> The goal of the review process is to improve the proposal under review
> through constructive criticism and, eventually, determine the direction of
> Swift. When writing your review, here are some questions you might want to
> answer in your review:
> - What is your evaluation of the proposal?
> - Is the problem being addressed significant enough to warrant a
> change to Swift?
> - Does this proposal fit well with the feel and direction of Swift?
> - If you have used other languages or libraries with a similar
> feature, how do you feel that this proposal compares to those?
> - How much effort did you put into your review? A glance, a quick
> reading, or an in-depth study?
> More information about the Swift evolution process is available at
> Thank you,
> -Doug Gregor
> Review Manager
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution