Re: [swift-evolution] [Proposal] Replace all Swift comments by end notes.

-1 Comments should be part of the “flow of thought”. Moving them away from where they are needed is counter productive. Note that you can never force a bad programmer to become good. Regards, Rien Site: http://balancingrock.nl Blog: http://swiftrien.blogspot.com Github:

Re: [swift-evolution] [Proposal] Replace all Swift comments by end notes.

On 16 Jan 2017, at 15:28, Amir Michail via swift-evolution wrote: > > Why not replace all Swift comments by end notes at the end of each source > file so as to minimize the impact of misleading/outdated comments on code > comprehension? A strong -1 from me. Moving

Re: [swift-evolution] [Proposal] Replace all Swift comments by end notes.

> On 16 Jan 2017, at 16:38, Amir Michail via swift-evolution > wrote: > > >> On Jan 16, 2017, at 10:55 AM, Tony Allevato wrote: >> >> As a general rule of thumb, changes to the language should not require the >> use of an IDE in order to

Re: [swift-evolution] [Proposal] Replace all Swift comments by end notes.

~Robert Widmann 2017/01/16 10:28、Amir Michail via swift-evolution のメッセージ: > Why not replace all Swift comments by end notes at the end of each source > file so as to minimize the impact of misleading/outdated comments on code > comprehension? The location of

Re: [swift-evolution] [Proposal] Replace all Swift comments by end notes.

-1 from me. I prefer at-site documentation rather than having to scroll through potentially hundreds of comments at the end of the file (each of which would then have to have additional data to provide context information that isn't needed as it currently stands. I fully understand (and agree)

Re: [swift-evolution] [Proposal] Replace all Swift comments by end notes.

> On Jan 16, 2017, at 8:29 PM, Karl Wagner via swift-evolution > wrote: > > >> On 16 Jan 2017, at 20:26, David Sweeris via swift-evolution >> wrote: >> >> >> >>> On Jan 16, 2017, at 09:28, Amir Michail via swift-evolution >>>

Re: [swift-evolution] [Proposal] Replace all Swift comments by end notes.

> On 16 Jan 2017, at 20:26, David Sweeris via swift-evolution > wrote: > > > >> On Jan 16, 2017, at 09:28, Amir Michail via swift-evolution >> wrote: >> >> Why not replace all Swift comments by end notes at the end of each source >>

Re: [swift-evolution] [Proposal] Replace all Swift comments by end notes.

> On Jan 16, 2017, at 09:28, Amir Michail via swift-evolution > wrote: > > Why not replace all Swift comments by end notes at the end of each source > file so as to minimize the impact of misleading/outdated comments on code > comprehension? > > You don’t

Re: [swift-evolution] [Proposal] Replace all Swift comments by end notes.

> On Jan 16, 2017, at 5:38 PM, Amir Michail via swift-evolution > wrote: > > >> On Jan 16, 2017, at 10:55 AM, Tony Allevato wrote: >> >> As a general rule of thumb, changes to the language should not require the >> use of an IDE in order

Re: [swift-evolution] [Proposal] Replace all Swift comments by end notes.

> On Jan 16, 2017, at 10:55 AM, Tony Allevato wrote: > > As a general rule of thumb, changes to the language should not require the > use of an IDE in order to return them back to the level of usability that was > had before the change. Swift is not a Mac/Xcode-only

Re: [swift-evolution] [Proposal] Replace all Swift comments by end notes.

On Mon, Jan 16, 2017 at 8:38 AM Amir Michail wrote: > > > On Jan 16, 2017, at 10:55 AM, Tony Allevato > wrote: > > > > As a general rule of thumb, changes to the language should not require > the use of an IDE in order to return them back to the level

Re: [swift-evolution] [Proposal] Replace all Swift comments by end notes.

As a general rule of thumb, changes to the language should not require the use of an IDE in order to return them back to the level of usability that was had before the change. Swift is not a Mac/Xcode-only language, and even on that platform, there are a number of times where I personally find

[swift-evolution] [Proposal] Replace all Swift comments by end notes.

Why not replace all Swift comments by end notes at the end of each source file so as to minimize the impact of misleading/outdated comments on code comprehension? You don’t necessarily need to scroll to the end of the source file to read a referenced end note in the code since the IDE could