If you’ve used Golang for any of your projects, you would have encountered with one of the following errors:
imported and not used: "X""X" declared but not used
Of course, it is a good feature to have because it tells you that you’ve got unused variables and
imports in your code. But the reason why it’s infuriating is because it impedes your development
speed. I personally am new to Golang and I’ve been working on a project called
gotem which is basically a glamorous clone of
tremc. Like most programmers, I use the most powerful debugging
tool ever, the print statement. For me to use the print statement in golang, I’ll have to import a
package named fmt and do fmt.Println() to print anything whatsoever. As I’m always adding and
commenting out or deleting fmt.Println’s all over the place, I end up facing the above mentioned
errors very frequently and in order for the code to run, I’ll have to go remove the import statement
and then remember to add it again when I add another fmt.Println again. I thought maybe there is a
way to disable this check via a flag or something and ended up searching for possible
solutions,
but the “solutions” are not that convincing.