> 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
myself working in Sublime Text instead of Xcode, for various reasons.
One could argue that those using a simple editor that can't hide comments
would benefit more from this proposal.
By removing the context that those comments can provide? It seems like
you're trying to argue both sides of an argument at the same time: this
feature is OK because IDEs can still show you the comments and you don't
have to scroll to the end of the file, but users without IDEs who will be
forced to scroll to the end of the file will still benefit because...?
It feels like your argument is just that comments can become out of date,
or they take up too much space/you want to see more of the code. For the
first, that's a problem that your proposal won't solve—it just moves the
outdated content to the end of the file where it can be ignored more
easily. That's not an improvement. For the second, I think most software
developers would *love* to have the problem of too much documentation in
their code vs. too little.
On Mon, Jan 16, 2017 at 8:38 AM Amir Michail <firstname.lastname@example.org> wrote:
> On Jan 16, 2017, at 10:55 AM, Tony Allevato <email@example.com> > wrote:
> Regarding this idea specifically, I think it would simply discourage
users from writing comments at all, without necessarily any improvement in
code quality. The developers who already write self-explanatory code will
continue to do so, and those who write bad code and don't comment will also
continue to do so. Do you have any evidence that making commenting harder
would improve code quality?
> On Mon, Jan 16, 2017 at 7:28 AM Amir Michail via swift-evolution < > firstname.lastname@example.org> 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
> 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
> Maybe this would encourage programmers to write more self-explanatory
code while keeping (end note) comments to a minimum?
> swift-evolution mailing list