[swift-evolution] [Review extension] SE-0030 Property Behaviors

[Shawn Erickson]

I personally like the functionality outlined in this proposal. Also *tip of
my hat* to those that have put together this proposal and prototype
implementation.

The biggest issue seems to be the syntax for it and it is becoming hard to
follow the discussion thread given all the – often nicely – outlined
alternatives.

I guess it isn't clear what of the alternatives are seriously being
considered, etc. ... as well as the state of the proposal potentially
incorporating these alternates.

If property behaviors are likely to be user definable in addition to a
canned set of behaviors provided by the standard library then I feel we
should attempt to avoid yet another methodology of name-spacing /
extending. I feel we should attempt to leverage existing language
methodologies as possible (for example the suggestion around consider
behaviors as an extension to var and let, etc.).

I don't have anything really to propose along those lines (still trying to
get a lot worked out in my head) but I wanted to express my first gut
feeling on this.

-Shawn


On Mon, Feb 15, 2016 at 2:38 PM Joe Groff via swift-evolution <
swift-evolution at swift.org> wrote:

> Hi everyone. In response to feedback, I've extended the review period for
> SE-0030 for another week. I've also decided to subset out *member access*
> from the initial proposal, as in accessing `x.[lazy].clear()` or other
> behavior-provided methods on a property. There's a lot of contention about
> the syntax, of course, but Michel Fortin and private reviewers have made
> good points that tying these "out-of-band" non-type members to properties
> is a feature that may not be best expressed as part of behaviors. Like many
> of the other topics that were factored out, the design space is deep enough
> that out-of-band member access deserves a design and review of its own.
> Thank you all for the feedback so far!
>
> -Joe
>
> On Feb 10, 2016, at 2:00 PM, Douglas Gregor via swift-evolution <
> swift-evolution at swift.org> wrote:
>
> Hello Swift community,
>
> The review of SE-0030 "Property Behaviors" begins now and runs through
> February, 2016. The proposal is available here:
>
>
> https://github.com/apple/swift-evolution/blob/master/proposals/0030-property-behavior-decls.md
> <https://github.com/apple/swift-evolution/blob/master/proposals/NNNN-proposal.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
>
> 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/0030-property-behavior-decls.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
>
> Thank you,
>
> Doug Gregor
>
> Review Manager
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160219/08647234/attachment.html>