Re: [swift-users] [Feature Request] Extend the `defer` statement

2017-10-09 Thread Jun Zhang via swift-users
Hi Jay, I'm wrong and please ignore the "Input parameter" because I can already get them within the defer statement body. Since we have a `newValue` keyword in `didSet` statement, I think a `returnValue` keyword will be fine. On Mon, Oct 9, 2017 at 4:49 PM, Geordie Jay

Re: [swift-users] [Feature Request] Extend the `defer` statement

2017-10-09 Thread Geordie Jay via swift-users
This feature request is probably one for swift evolution. I like the idea in theory, but I’d prefer to see the return value identifier being spelled out, i.e. “returnValue” instead of the symbols. Jun Zhang via swift-users schrieb am Mo. 9. Okt. 2017 um 05:37: > Yes

Re: [swift-users] [Feature Request] Extend the `defer` statement

2017-10-08 Thread Jun Zhang via swift-users
Yes that's true, but this requires me to set a return value in every `early return` statement. I think this should be done by the compiler instead of me, to make code cleaner and also less error-prone. On Mon, Oct 9, 2017 at 11:24 AM, Slava Pestov wrote: > I think you can

Re: [swift-users] [Feature Request] Extend the `defer` statement

2017-10-08 Thread Slava Pestov via swift-users
I think you can achieve what you want by having the ‘defer’ block capture a mutable local variable. Eg, func doStuff() { var success = false defer { if !success { // do some additional cleanup } } … success = true … return result } > On Oct 8, 2017, at 7:34 PM,

[swift-users] [Feature Request] Extend the `defer` statement

2017-10-08 Thread Jun Zhang via swift-users
Hi dear swift developers, I am kind of new to swift and I don't know if this feature already exists. And if it exists already please tell me how. Thank you very much! The feature is to capturing the return value (maybe input value also) of the function. Here is the demo code: func