4 ms·
I think this was a bad decision. I think you would agree as soon a tool emerges that follows your example and uses //todo: bar to do stuff with the code, and
by Merkur 11y ago
I think this was a bad decision. I think you would agree as soon a tool emerges that follows your example and uses
//todo: bar
to do stuff with the code, and makes the program fail because it's not done, because you don't know about it. with a #todo: bar the go tool chain would catch this error
- castell 11y agoIf the add "//Todo:" as syntax, many projects would be screwed. Abusing comments for anything else is not good.
- JadeNB 11y agoMaybe I have missed the point, but your post sounds like you think Merkur disagrees. I think that you are actually agreeing with the GP (https://news.ycombinator.com/item?id=9523335 https://news.ycombinator.com/item?id=9523335), which says that: > I think this was a bad decision. I think you would agree as soon [as] a tool ... uses > //todo: bar (i.e., that the `//todo:` syntax would unambiguously demonstrate the bad-ness of the decision).