7 ms·
I still find Go too tolerant on this. It should scan your Git history and stash as well, and fail to compile if it finds any unused code there.
by codeflo 3y ago
I still find Go too tolerant on this. It should scan your Git history and stash as well, and fail to compile if it finds any unused code there.
- SuperCuber 3y agoThat'd still be a bit too tolerant for my tastes. It should also scan your future commits.
- viscanti 3y agoThat'd still be a bit too tolerant for my tastes. It should have some kind of reinforcement signal that's stronger than just preventing the code from compiling. Some kind of shock therapy to help users learn and internalize things might be more appropriate here.
- lainga 3y agogo vet -basilisk ./...
- yobert 3y agoReally it needs to scan my coworkers commits as well. Can't be too careful.
- jerf 3y agoAh, I know the programming language for you: https://news.ycombinator.com/item?id=5002597 https://news.ycombinator.com/item?id=5002597
- mseepgood 3y agoCould you please expand on this? Why would local Git stashes relate to code quality?
- erik_seaberg 3y agoThat comment might not be entirely serious.