[swift-evolution] Cancelable named defer statements

[Xiaodi Wu]

-1. Much of the utility of `defer` is that it's guaranteed to execute. As
you demonstrate, it's possible to capture a flag and choose not to do
something within the defer block itself. We don't need sugar for that.

On Sat, Jan 7, 2017 at 12:20 PM, Rien via swift-evolution <
swift-evolution at swift.org> wrote:

> Is there any interest in a proposal to introduce a named defer statement
> that can be cancelled?
>
> Lately I find myself writing this kind of code:
>
> func openFile(kind: String) -> UnsafeMutablePointer<FILE>? {
>
>
>     var file = fopen("MyFile.txt", "r")
>
>
>     var closeFile = true
>
>     defer { if closeFile { fclose(file) } }
>
>
>     if fileIsNotValid(file) { return nil }
>
>     if fileDoesNotContainsData(file, kind) { return nil }
>
>
>     if fileDataOutOfDate(file) { return nil }
>
>
>     // Prevent the deferred handler from closing the file
>     closeFile = false
>
>     return file
> }
>
> Which imo would be much cleaner if we were able to write:
>
> func openFile(kind: String) -> UnsafeMutablePointer<FILE>? {
>
>     var file = fopen("MyFile.txt", "r")
>
>     CLOSE_FILE: defer { fclose(file) }
>
>     if fileIsNotValid(file) { return nil }
>
>     if fileDoesNotContainsData(file, kind) { return nil }
>
>     if fileDataOutOfDate(file) { return nil }
>
>     // Prevent the deferred handler from closing the file
>     cancel CLOSE_FILE
>
>     return file
> }
>
> Regards,
> Rien
>
> Site: http://balancingrock.nl
> Blog: http://swiftrien.blogspot.com
> Github: http://github.com/Swiftrien
> Project: http://swiftfire.nl
>
> _______________________________________________
> 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/20170107/fb550540/attachment.html>