-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: http://github.com/Swiftrien Project: http://swiftfire.nl > On 17 Jan 2017, at 12:30, Alex Blewitt via swift-evolution > <[email protected]> wrote: > > On 16 Jan 2017, at 15:28, Amir Michail via swift-evolution > <[email protected]> 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 comments aside from the place where the code is > defined is going to maximise outdated comments, not minimise it. > >> 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 show a popup whenever >> the mouse pointer lingers over an end note reference (e.g., a number/label). >> >> Maybe this would encourage programmers to write more self-explanatory code >> while keeping (end note) comments to a minimum? > > This proposal would certainly discourage having accurate comments. > > Alex > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
