-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathatom.xml
More file actions
31 lines (24 loc) · 1.83 KB
/
atom.xml
File metadata and controls
31 lines (24 loc) · 1.83 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title><![CDATA[Fellowswift]]></title>
<link href="http://fellowswift.github.io/atom.xml" rel="self"/>
<link href="http://fellowswift.github.io/"/>
<updated>2016-01-14T10:50:31+01:00</updated>
<id>http://fellowswift.github.io/</id>
<author>
<name><![CDATA[Fellowswift]]></name>
<email><![CDATA[fellowswift@gmail.com]]></email>
</author>
<generator uri="http://octopress.org/">Octopress</generator>
<entry>
<title type="html"><![CDATA[The @noescape Tag Purpose and Why It Must Be Explicitly Applied]]></title>
<link href="http://fellowswift.github.io/blog/2016/01/13/the-at-noescape-tag-purpose-and-why-it-must-be-explicitly-applied/"/>
<updated>2016-01-13T21:49:49+01:00</updated>
<id>http://fellowswift.github.io/blog/2016/01/13/the-at-noescape-tag-purpose-and-why-it-must-be-explicitly-applied</id>
<content type="html"><![CDATA[<p>Earlier this week <a href="https://github.com/dcordero">I</a> had a very interesting discussion about <code>@autoclosures</code> and <code>@noescape</code> tags with <a href="https://github.com/phelgo">@phelgo</a>, as result of which we wondered the whys of some decision in the design of Swift’s syntax.</p>
<p>More specifically we wondered about why the tag <code>@noescape</code> isn’t automatically detected and it needs to be explicitly applied. Because… In fact, it is somehow detected at compile time, because trying to add the @noescape tag to a func with escaping closures results in an compilation error.</p>
<p>So the question was why… why <code>@noescape</code> needs to be explicitly added and Apple did not create it to be automatically added when it is needed?</p>
<p>After some researches and different inputs…</p>
]]></content>
</entry>
</feed>