> Xcode creates warning as you type
And the warnings also tend to obscure my typing (rdar://27141386 - warning
box occludes typing when trying to fix a warning).
I turn live issues off (even though that kind of breaks playground error
reporting - rdar://27162167 - playgrounds don't show any
A try that isn't needed is suspicious… but imho there is a problem with
warnings, but that isn't primarily caused by Swift itself.
Xcode creates warning as you type, and those often don't help, but just
distract, as most of them aren't actually dangerous at all:
- Yes, I'm not using this value
> On 7 Jul 2016, at 23:28, John McCall via swift-evolution
> wrote:
>
>> On Jul 7, 2016, at 3:26 PM, Chris Lattner via swift-evolution
>> wrote:
>>> On Jul 7, 2016, at 10:58 AM, Vladimir.S via swift-evolution
>>>
> On Jul 7, 2016, at 3:26 PM, Chris Lattner via swift-evolution
> wrote:
>> On Jul 7, 2016, at 10:58 AM, Vladimir.S via swift-evolution
>> wrote:
>>
>> I didn't expect this is allowed(with warning):
>>
>> try print("foo")
>>
>> (Swift
> On Jul 7, 2016, at 10:58 AM, Vladimir.S via swift-evolution
> wrote:
>
> I didn't expect this is allowed(with warning):
>
> try print("foo")
>
> (Swift Ver. 3.0 (Jun 20, 2016))
>
> Do we really need to allow 'try' for functions that does not throw exceptions?
> On 7 Jul 2016, at 19:41, David Sweeris via swift-evolution
> wrote:
>
>
>> On Jul 7, 2016, at 12:58, Vladimir.S via swift-evolution
>> wrote:
>>
>> I didn't expect this is allowed(with warning):
>>
>> try print("foo")
>>
>> (Swift
> On Jul 7, 2016, at 12:58, Vladimir.S via swift-evolution
> wrote:
>
> I didn't expect this is allowed(with warning):
>
> try print("foo")
>
> (Swift Ver. 3.0 (Jun 20, 2016))
>
> Do we really need to allow 'try' for functions that does not throw exceptions?
I didn't expect this is allowed(with warning):
try print("foo")
(Swift Ver. 3.0 (Jun 20, 2016))
Do we really need to allow 'try' for functions that does not throw exceptions?
___
swift-evolution mailing list
swift-evolution@swift.org