Re: Handle '//:lint' and '//:nolint' comments. (issue 7801048)

[usrb...@yahoo.com]

Thanks for the commit. I promise, you'll love traceur's regained
semicolon-checking powers so much that you'll forget about the code
that makes it possible.

I apologize in advance for the extra contortion coming in my next
pull request.

Here is where I metaphorically lock the doors and turn the lights out
before leaving the codereview building for the last time.

I'm glad I got the chance to get the codereview experience -- I can
see the strengths and weaknesses of github that much more clearly,
having something to compare it against.

A github pull request corresponds roughly to a single patch set of
a codereview issue. I think if github made it possible to deal with
pull requests the way codereview deals with patch sets, that would
be the ultimate combination.

And seriously, github, don't make pieces of the pull request
suddenly morph and disappear just because someone did a
'git push -f'! [end rant]

I feel like codereview seems to foster a more careful approach. I know
that constant iteration is still the side to bet on, but I can't help
thinking that this needs to be tempered with periods of more
thoughtfulness.

I'm sure I'll feel nostalgic about github when the time comes, but
we'll cross that bridge when we get to it (when the more frenetic
successor to github takes over).


https://codereview.appspot.com/7801048/