<div dir="ltr">Hi!<div><br></div><div>I'd like to resurface this thread. Is this something that deserves a fully-fledged proposal? Should we add this to the @warn_unused_result by-default<span style="line-height:1.5"> proposal? <a href="https://github.com/apple/swift-evolution/pull/191/files">https://github.com/apple/swift-evolution/pull/191/files</a></span></div><div><span style="line-height:1.5"><br></span></div><div><span style="line-height:1.5">Thanks!</span></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Feb 8, 2016 at 8:44 PM Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>I sincerely apologize for the lack of professionalism in my response. I will try to maintain higher standards in future communication.</div><div><br></div><div>Best regards. -- E</div></div><div style="word-wrap:break-word"><br><div><blockquote type="cite"><div>On Feb 8, 2016, at 9:41 PM, Vanderlei Martinelli <<a href="mailto:vmartinelli@alecrim.com" target="_blank">vmartinelli@alecrim.com</a>> wrote:</div><br><div><div dir="ltr">@EricaSadun I’d like to say that many of us are not native English speakers. I had to find what is the meaning of “gimme” and “dunno”. And it is a good thing, so I can learn more English words and slangs. But at the same time sometimes I read these messages in a place where it is not possible to consult dictionaries or when I just do not have time to do this.<div><br></div><div>OK... Let’s explain the words:</div><div><br></div><div>gimme. noun. <span style="font-family:-apple-system;font-size:13px">a thing that is very easy to perform or obtain, <span>especially</span> in a game or sport<span>:</span><span></span></span><span style="font-family:-apple-system;font-size:13px"><span style="font-style:italic"> the kick would hardly be a gimme in that wind</span></span><br><div><br></div><div>dunno. contraction. <span style="font-size:13px;font-family:-apple-system">(I) do not know</span><span style="font-size:13px;font-family:-apple-system">. origin </span><span style="font-size:13px;font-family:-apple-system"><span><span>mid</span> 19<span>th</span> cent.</span></span><span style="font-size:13px;font-family:-apple-system">: </span><span style="font-size:13px;font-family:-apple-system">representing</span><span style="font-size:13px;font-family:-apple-system"> an informal </span><span style="font-size:13px;font-family:-apple-system">pronunciation</span><span style="font-size:13px;font-family:-apple-system">.</span></div><div><br></div></div><div>;-)<br></div><div><br></div><div>Dunno, but the more we use internationally known words may be a gimme to track the subject that is Swift evolution.<br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 9, 2016 at 1:47 AM, Erica Sadun via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
> On Feb 8, 2016, at 8:32 PM, Joe Groff via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
><br>
><br>
>> On Feb 8, 2016, at 7:25 PM, Joe Groff via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
>><br>
>> Javier Soto brought up a case where his ReactiveCocoa code silently did the wrong thing by implicitly discarding the result of a closure:<br>
>><br>
>> <a href="https://twitter.com/Javi/status/695680700033306624" rel="noreferrer" target="_blank">https://twitter.com/Javi/status/695680700033306624</a><br>
>><br>
>> Since it sounds like we plan on making `@warn_unused_result` the default, it seems natural to also warn when a closure has its result type converted away to Void. If there's one 'return' statement, we could dive into the return expression to decide whether to warn based on the function whose result is getting ignored.<br>
><br>
> There's another axis of intent in whether the closure was written with an explicit return or not. `{ foo($0) }` is ambivalent to whether it intends to propagate the value returned by `foo` or not, whereas `{ return foo($0) }` is explicitly trying to do so. IMO we have a stronger case to warn if the `return` is explicit in the closure body.<br>
<br>
<br>
</span>if foo is -> Void, it's a gimme.<br>
if foo is -> T with @warn_unused_result, it's a gimme<br>
if foo is -> T without @warn_unused_result, dunno<br>
<span><font color="#888888"><br>
-- E<br>
</font></span><div><div><br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</div></div></blockquote></div><br></div>
</div></blockquote></div><br></div>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div><div dir="ltr">-- <br></div><div dir="ltr">Javier Soto</div>