所以啊,程序员的 TODO 。。。。
所以啊,程序员的 TODO 。。。。
|
noqwertyFeb 27, 2021 via Android
1
哈哈,又不是不能用.jpg
|
|
2
重命名成 permanentFix,todo 立刻移除
|
|
SeddasFeb 27, 2021 via iPhone
3
这算啥,我见过七八年的 todo
|
|
4
todo means never do
|
|
hlwjiaFeb 27, 2021 via iPhone
5
只能说这个 fix 写地很耐用
|
|
6
TODO 意思是 I have an idea
|
|
seven2fFeb 27, 2021
7
只要不是计划需求,能 do 的都 do 了,to do 的 never to do
|
|
12101111Feb 27, 2021
8
17 year old Firefox feature request fixed:
https://news.ycombinator.com/item?id=26256459 |
|
fucUupFeb 27, 2021
9
做就是爱, 不做证明你不爱
|
|
git00llFeb 27, 2021
10
todo 补充这里的注释
|
|
mingl0280Feb 27, 2021 via Android
11
我一般会在写完一个项目以后用 todo explorer 扫一下代码看看还剩啥 todo 没,有的话赶紧给实现了。
|
|
13
Use TODO comments for code that is temporary, a short-term solution, or good-enough but not perfect.
TODOs should include the string TODO in all caps, followed by the name, e-mail address, bug ID, or other identifier of the person or issue with the best context about the problem referenced by the TODO. The main purpose is to have a consistent TODO that can be searched to find out how to get more details upon request. A TODO is not a commitment that the person referenced will fix the problem. Thus when you create a TODO with a name, it is almost always your name that is given. ``` // TODO([email protected]): Use a "*" here for concatenation operator. // TODO(Zeke) change this to use relations. // TODO(bug 12345): remove the "Last visitors" feature. ``` If your TODO is of the form "At a future date do something" make sure that you either include a very specific date ("Fix by November 2005") or a very specific event ("Remove this code when all clients can handle XML responses."). 出自: https://google.github.io/styleguide/cppguide.html#TODO_Comments |
|
14
我寻思能工作三年的 temporaryFix 的质量,早就经过实践检验,可以称得上是 stableFix 了。
|