5 ms·

And I can add additional information next to the todo: // todo: todo

• bee_rider 4y ago
  As long as the second todo is also standardized (TODO: FIXME), so it will play nicely with grep.
• zeven7 4y ago
  This is my real gripe. Let's not pretend "TODO" is the end of the comment.
  • masklinn 4y ago
    Nobody did? The article's goal is clearly to provide a quick categorisation of the TODO, rather than require reading the description to discover it: if I'm trying to debug something and reach a bit of code with a bunch of TODOs it's not going to help me much, if I see a FIXME or BUG I'm going to be a lot more interested. Sometimes the TODO us sufficient through it context (e.g. a docstring empty but for a TODO stanza is obviously a missing doc), but often it's not and is the documentary equivalent of a goto.
    • marcosdumay 4y ago
      The article is clearly to break our tools and search capacity. If you want to add categorization, do add, instead of replacing, like the GP does.
      • masklinn 4y ago
        > The article is clearly to break our tools and search capacity. Get yourself tools which are not hot garbage? All the ones I use let you customise markers however you want.
        • ahtihn 4y ago
          > All the ones I use let you customise markers however you want Customisation requires everyone who ever works on that codebase to also do the customization. Defaults are important
          • masklinn 4y ago
            > Customisation requires everyone who ever works on that codebase to also do the customization. And they can go on the pile of all the others customisations necessary when you don't mandate all the tooling by fiat. > Defaults are important Defaults are a tool, when they hinder improvement you discard them.