> On May 2, 2017, at 6:44 PM, Jon Shier via swift-evolution > <swift-evolution@swift.org> wrote: > I’m not a language or memory expert, so I think the proposal could use > a few more examples of the code it would disallow. Perhaps examples from real > world projects? Without being an expert I’m having a hard time seeing the > full impact of the proposed rules.
We hope that there will not be any widespread examples from real-world projects that run afoul of the rule. If the examples seem a little contrived, that's good; we believe the rule is almost always already followed. > Also, the @exclusivity syntax doesn’t seem fully defined. Is there a > @exclusivity(checked) counterpart? Yes, which would be the default (on class properties and global variables). > Would subclasses be allowed to mark inherited properties more or less > strictly? No. The rule has to be established by the place which creates the storage. > Also, is the logic for @ attributes and keyword attributes documented > anywhere? Otherwise it seems like exclusive / nonexclusive would be an option. The guidelines about when to use an @ attribute and when to use a keyword attribute are always a bit uncertain, but in this case I think they clearly point us towards an @ attribute. This is an attribute which opts in to unsafe behavior for performance reasons; it is not expected to be important enough to warrant a keyword. John. > > > > Jon > >> On May 2, 2017, at 4:07 PM, Ben Cohen via swift-evolution >> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote: >> >> Hello Swift community, >> >> The review of SE-0176: "Enforce Exclusive Access to Memory" begins now and >> runs through May 8, 2017. >> >> The proposal is available here: >> >> https://github.com/apple/swift-evolution/blob/master/proposals/0176-enforce-exclusive-access-to-memory.md >> >> <https://github.com/apple/swift-evolution/blob/master/proposals/0176-enforce-exclusive-access-to-memory.md> >> Reviews are an important part of the Swift evolution process. All reviews >> should be sent to the swift-evolution mailing list at: >> >> https://lists.swift.org/mailman/listinfo/swift-evolution >> <https://lists.swift.org/mailman/listinfo/swift-evolution> >> 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: >> >> https://github.com/apple/swift-evolution/blob/master/proposals/0176-enforce-exclusive-access-to-memory.md >> >> <https://github.com/apple/swift-evolution/blob/master/proposals/0176-enforce-exclusive-access-to-memory.md> >> Reply text >> >> Other replies >> >> <https://github.com/apple/swift-evolution#what-goes-into-a-review-1> >> 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: >> >> https://github.com/apple/swift-evolution/blob/master/process.md >> <https://github.com/apple/swift-evolution/blob/master/process.md> >> >> Thanks, >> Ben Cohen >> Review Manager >> >> _______________________________________________ >> swift-evolution mailing list >> swift-evolution@swift.org <mailto:swift-evolution@swift.org> >> https://lists.swift.org/mailman/listinfo/swift-evolution >> <https://lists.swift.org/mailman/listinfo/swift-evolution> > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org <mailto:swift-evolution@swift.org> > https://lists.swift.org/mailman/listinfo/swift-evolution > <https://lists.swift.org/mailman/listinfo/swift-evolution>
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
