3 ms·

Real question: For other languages, like C and C++, that warn about unused variables, do you ignore these warnings? When would it be a good idea to allow unuse

• mst 2y ago
  Between commits when I'm still modifying things. There's plenty of stuff that I have checked by a lint test before commit but is allowed to stick around in the codebase for a while locally as I work. e.g. if I have a debugging function that I'm adding/removing calls to a lot I'd like to be able to leave the import for it in place until I'm done even if my current step isn't using it.
• superb_dev 2y ago
  Actually go doesn’t have warnings, only errors. (Unused variables trigger a compile error)