[swift-evolution] Annotation of Warnings/Errors

[Alejandro Martinez]

I don't think this is a language issue, as said warnings and fix-its
are really useful.
In the other handm when watching other programmers in other languages
without IDE triggering a compile trough the terminal I see that it
allows them to put all their ideas into code first, and then deal with
warnings or errors.

The solution seems just to be "Go to preferences and select the
“General” tab. Make sure that “show live issues” is deselected". At
the end, any option to turn on or off warnings (or even show them at
specific times) should be a setting in the IDE as currently is in
Xcode.

On Sat, Feb 4, 2017 at 1:45 AM, Derrick Ho via swift-evolution
<swift-evolution at swift.org> wrote:
> I feel like warnings showing up as you type are an IDE's responsibility.
>
> Annotations to delay warnings seem like noise.  Once you get used to
> programming you don't need the annotations.
>
> If warnings are bothersome, then turn it off in the Xcode settings!
>
>
>
>
> On Thu, Feb 2, 2017 at 1:34 PM Pierre Monod-Broca via swift-evolution
> <swift-evolution at swift.org> wrote:
>>
>> +1 to the proposal
>> +1 to teach how to remove live issues to beginners, so they have a chance
>> to train at detecting errors without the compiler
>>
>>
>>
>> Pierre
>>
>> Le 2 févr. 2017 à 17:48, Nicolas Fezans via swift-evolution
>> <swift-evolution at swift.org> a écrit :
>>
>> +1
>>
>> On Tue, Jan 31, 2017 at 11:55 AM, Tino Heth via swift-evolution
>> <swift-evolution at swift.org> wrote:
>>>
>>> One of the biggest issues that I saw while teaching Swift to newbies
>>> (most had not programmed before) is confusion based on the early
>>> warnings/errors that swift/xcode gives you as they type.  What would happen
>>> is that they would type a variable, and it would say… “You haven’t used this
>>> variable” and so they would just click the fixit because they trust the
>>> compiler more than they trust themselves.  This would lead to a point where
>>> they were very confused because some of the code was code they had thought
>>> through, and some of it was changed by random fixits in ways they didn’t
>>> understand… and so it would lead to more errors/fixits until they had errors
>>> which couldn’t be fixed.
>>>
>>>
>>> Imho this is the best example to illustrate that inflationary use of
>>> warnings does more harm than good, and I hope it will be fixed.
>>>
>>> Having a bunch of conditions for warnings looks like overkill to me, and
>>> there are alternatives:
>>> - Only show when building
>>> - Only show in release builds
>>> - Linter
>>>
>>> That said, I'm going out on a limb and claim I already know how to write
>>> code and don't need basic schooling, and showing warnings before I hit
>>> compile is merely a distraction.
>>>
>>> But there are also Playgrounds which seem to be an important aspect of
>>> Swift, especially for newbies who could really benefit from some hints.
>>> There are no linters, no release builds, and even no regular builds for
>>> Playgrounds, so your model is the only one that works for them.
>>>
>>> Bottom line:
>>> +1
>>>
>>> _______________________________________________
>>> swift-evolution mailing list
>>> swift-evolution at swift.org
>>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>>
>>
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org
>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org
>> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>



-- 
Alejandro Martinez
http://alejandromp.com