[swift-evolution] [swift-evolution-announce] [Review] SE-0176: Enforce Exclusive Access to Memory
howard.lovatt at gmail.com
Sat May 13 01:43:38 CDT 2017
+1, the benefits outweigh the extra restrictions. Particularly since it is
easy to add an escaping annotation if you think the compiler is wrong.
However this will require careful documentation and good error messages so
that people know why it fails to type check and how to overcome that.
On 13 May 2017 at 12:29, Ben Cohen <ben_cohen at apple.com> wrote:
> Hello Swift community,
> The review of revisions to *SE-0176: **Enforce Exclusive Access to Memory* begins
> now and runs through *May 17, 2017*.
> Most of this proposal was previously *accepted*. An implementation issue
> has been discovered with the use of dynamic enforcement on inout
> parameters. The proposal implementors suggest adopting a stronger rule
> governing the use of non-escaping closures which will also allow Swift to
> make firm guarantees about the use of static enforcement when a variable
> does not escape. The core team tentatively supports this new rule but
> believes it is a substantial enough revision that it requires a separate
> review period.
> The proposal is available here: https://github.com/
> Since this is a review of revisions only, you may find these two relevant
> commits easier:
> 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
> What 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,
> swift-evolution-announce mailing list
> swift-evolution-announce at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution