<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Closures on dev.endevour</title><link>https://devendevour.iankulin.com/tags/closures/</link><description>Recent content in Closures on dev.endevour</description><generator>Hugo</generator><language>en-AU</language><lastBuildDate>Mon, 25 Jul 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://devendevour.iankulin.com/tags/closures/index.xml" rel="self" type="application/rss+xml"/><item><title>Closures</title><link>https://devendevour.iankulin.com/closures/</link><pubDate>Mon, 25 Jul 2022 00:00:00 +0000</pubDate><guid>https://devendevour.iankulin.com/closures/</guid><description>&lt;p&gt;I had one of those synchronicity in learning moments this morning. I am reading &lt;a href="https://docs.swift.org/swift-book/" target="_blank" rel="noopener"&gt;The Swift Book&lt;/a&gt; - ie &lt;em&gt;The Swift Programming Language, Swift 5.7&lt;/em&gt; as part of my cs193p homework, and this morning, in a coffee shop was admiring what a clear, well written explanation was given for &lt;a href="https://docs.swift.org/swift-book/LanguageGuide/Closures.html" target="_blank" rel="noopener"&gt;closures&lt;/a&gt; . It is super well written, stepping the reader through in logical (and digestible) steps.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;ve never carelessly passed around a pointer to a function and caused the Blue Screen of Death, or done much multi-threaded programming, the use-case for closures, and use of them is going to be challenging at first. Then Swift&amp;rsquo;s ability to cut the syntax down to very little will be challenging.&lt;/p&gt;</description></item></channel></rss>