<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br>~Robert Widmann</div><div><br>2017/01/16 10:28、Amir Michail via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> のメッセージ:<br><br></div><blockquote type="cite"><div><span>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?</span><br></div></blockquote><div><br></div><div>The <i>location</i> of code comments was never the issue.</div><br><blockquote type="cite"><div><span></span><br><span>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).</span><br></div></blockquote><div><br></div><div>As others have noted, it is really not a good idea to introduce features predicated on the existence of Xcode.</div><div><br></div><blockquote type="cite"><div><span></span><br><span>Maybe this would encourage programmers to write more self-explanatory code while keeping (end note) comments to a minimum?</span><br></div></blockquote><div><br></div><div>This seems like it is just going to encourage a huge unmaintainable book being written at the end of every file. The ratio of documentation to code in some libraries is 10-or-20-to-1 in some cases.</div><div><br></div><div>It seems like this proposal has a scaling problem.</div><br><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>