[Proposal] Property behaviors
Will property behaviors work on computed properties? Because for now, we can change a storage to a computed property and a computed for a storage property without breaking anything. ··· (click for...
View Article[Proposal] Property behaviors
Will property behaviors work on computed properties? Because for now, we can change a storage to a computed property and a computed for a storage property without breaking anything. I'm not sure...
View Article[Proposal] Property behaviors
You're glossing over some of the subtleties of initialization. Recall that a "plain old" stored property can be initialized out-of-line: func foo() { var x: Int ... x = 1 } struct Bar { var y:...
View Article[Proposal] Property behaviors
You're glossing over some of the subtleties of initialization. Recall that a "plain old" stored property can be initialized out-of-line: func foo() { var x: Int ... x = 1 } struct Bar { var y:...
View Article[Proposal] Property behaviors
I feel like, once you start stretching your design this way, we don't end up with something that's all that much simpler than what I've proposed. To help make review more digestible, I am planning to...
View Article[Proposal] Property behaviors
I've revised my proposal again based on more feedback. Syntax changes include: - adopting John McCall's declaration-follows-use syntax for behavior declarations. I think this looks nice and provides a...
View Article[Proposal] Property behaviors
Hi Joe, I have a few of questions after reading your proposal. Question #1 : Let’s say that the property behavior has an init() method as in your example for the lazy property behavior where you...
View Article[Proposal] Property behaviors
changing the proposed syntax for behavior member lookup to 'property.[behavior].member', as suggested by Tal Atlas and others. I think this has a nice symmetry with the `var [behavior]` declaration...
View Article[Proposal] Property behaviors
Hi Joe, I have a few of questions after reading your proposal. Question #1 : Let’s say that the property behavior has an init() method as in your example for the lazy property behavior where you...
View Article[Proposal] Property behaviors
Practically speaking, I think there are inevitably going to be breaking changes here once we get some experience with the feature. It won't ship until 3.0 at the earliest. Many of the other features...
View ArticleClik here to view.
[Proposal] Property behaviors
This is an excellent update. Simplifying the proposal provides a strong starting point without foreclosing solutions to some of the thorny cases addressed in the original proposal. It will be good to...
View Article[Proposal] Property behaviors
changing the proposed syntax for behavior member lookup to 'property.[behavior].member', as suggested by Tal Atlas and others. I think this has a nice symmetry with the `var [behavior]` declaration...
View Article[Proposal] Property behaviors
I hope we'll have the feature stabilized by then, of course. However, it's a strong goal for this feature to be "zero-cost" with little or no runtime footprint. If we're successful at that, there...
View Article[Proposal] Property behaviors
I must say that I really love your idea of property behaviours! I think a facility of this kind would be a great enhancement to Swift. I probably will have some more comments after I study your...
View Article[Proposal] Property behaviors
I must say that I really love your idea of property behaviours! I think a facility of this kind would be a great enhancement to Swift. I probably will have some more comments after I study your...
View Article[Proposal] Property behaviors
I don’t know enough about how ABIs work, but if this is out of scope for Swift 3, is there a way to add some “reserved for future use” bits or something now so that the ABI changes less often? It’d be...
View Article[Proposal] Property behaviors
Good point! I think making behaviors "zero-cost“ is a great idea! -Thorsten ··· (click for more details) Read full topic
View Article[Proposal] Property behaviors
Finally caught up. :-) I like this latest version better than the two previous versions, but I kind of think that if behaviors can't emulate "lazy", we've failed. Nothing has a stronger motivation...
View Article[Proposal] Property behaviors
Finally caught up. :-) I like this latest version better than the two previous versions, but I kind of think that if behaviors can't emulate "lazy", we've failed. Nothing has a stronger motivation...
View Article[Proposal] Property behaviors
Finally caught up. :-) I like this latest version better than the two previous versions, but I kind of think that if behaviors can't emulate "lazy", we've failed. Nothing has a stronger motivation...
View Article
