@noracodes *torrenting has entered the chat*
@jorin 🥺👉👈
@piegames @fasterthanlime Then maybe unused imports shouldn't be an error, at least that's the side I would come down on if I was creating a language
I would rather have a separate utility for my language for cleaning up code formatting and imports and such
@Gottox yes?? Why not?
I think that warnings are useless, cause people end up ignoring warnings if there are a lot of them
So, as a compiler writer you have to pick, is it a problem or not? Go chooses errors, other languages chooses to just ignore, Both choices are ok in my opinion
In go you can also just do the following to get rid of the error:
_ = x
Not quite 30, but Linux today will happily execute a binary compiled 27 years ago (15 Jun 1996)~ ✨
@fasterthanlime one thing I like about Go, if I remember correctly, is that they have a policy against compiler warnings, either it's something you must fix our it's not, and people tend not to fix warnings
"To be fair to C and C++, if you set yourself the goal of crossing an 8-lane freeway blindfolded, it does make sense to focus on doing it as fast as you possibly can." 😬
Trans woman, bisexual, someone's fiancée, forever a programmer, poly, and former total mess
Avatar by mavica