Jean de Klerk
|| at May 12, 2014 at 1:53 am
I suppose I had thought that TODOs in a complex project would be contained
in something like github issues or some other issue/feature tracking thing,
rather than lying around in code.
However, I'm pretty new to code bases of this size, so I wouldn't know
either way. Just seemed odd.
Maybe a better question would be, "How do the go dev folks keep track of
issues/features outside of TODOs, and how do they correlate their (tickets,
github issues, etc) to the TODO sitting in code?"
On Sunday, May 11, 2014 8:42:48 PM UTC-4, David Symonds wrote:
I'm not sure what you're asking. TODOs mark things that are yet to be
done, either because people haven't had the time or knowledge to do
them, or aren't in a hurry to do them. They're perfectly normal in
large code bases.
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]
For more options, visit https://groups.google.com/d/optout.