Re:Plotting the source code “TODO” history of the most popul...
by mekkkkkk on Monday May 17, 2021 @04:30AM
(#27181216)
The growing number is hardly surprising, yet I don't know exactly what the implications are. There are a lot of different categories of TODOs, ranging from harmless ("it would be nice if this was improved at some point") to critical ("this is a really bad solution that needs to be fixed ASAP"). I wonder if these repos has official definitions of what a TODO entails.
[ Parent
| on HN ]
Re:Plotting the source code “TODO” history of the most popul...
by mnahkies on Monday May 17, 2021 @04:49AM
(#27181336)
Perhaps we should be including a priority in such comments, eg:
TODO: high: don't use bogosort
Would only be useful if it became a defacto standard though
Re:Plotting the source code “TODO” history of the most popul...
by esyir on Monday May 17, 2021 @05:14AM
(#27181465)
At that point, make an issue and add it to the tracker.
Re:Plotting the source code “TODO” history of the most popul...
by schleiss on Monday May 17, 2021 @05:14AM
(#27181467)
Yes, I agree. Priority and some context on what to do instead. Because as soon as it's a standard, big software vendors like Jetbrains could automatically categorize and mark the various lines.
Re:Plotting the source code “TODO” history of the most popul...
by spockz on Monday May 17, 2021 @05:46AM
(#27181632)
Back when I used Eclipse there was another level called “FIXME”. Maybe it works in IntelliJ as well.
Re:Plotting the source code “TODO” history of the most popul...
by tirpen on Monday May 17, 2021 @08:38AM
(#27182753)
It does.
At least it works in PyCharm, so most likely it works in all IntelliJ based IDEs.
Re:Plotting the source code “TODO” history of the most popul...
by ExtraE on Monday May 17, 2021 @12:14PM
(#27185130)
Yes, it does. In fact, you can configure it to use whatever you want. (I have it also match BUG as another priority)