Many packages expose useful variables that are not being used themselves, like useful defaults for example. I guess this would be an argument in favor of limiting this kind of behaviour to inside the functions.
A good example is image/color/pallete. Also, there is some shenanigans on estimating the life of a variable that exists in global scope, but i'm still learning about compilers to say anything useful about this. On Tue, 2 Mar 2021, 14:37 Jad, <d...@madi.se> wrote: > Hi, > I'm new to Go and I would like to understand why the compilation process, > both the compiler and linker, does raise an error for a declared but not > used variable at funcs level in order to ensure clean code while the linker > does not raise this error during the build process for declared but not > used variables at package level but treat them as 'dead code' and silently > remove them. > > I asked on other mediums. Specifically Go Forum and #Go-nuts IRC and some > more experienced gophers said this might constitute a bug, at least at > philosophical level as it doesn't directly affect the build process. > > Best, > Jad > > > > -- > 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 golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/b13a26ae-5662-4b74-af2d-6c9e6dbeb425n%40googlegroups.com > <https://groups.google.com/d/msgid/golang-nuts/b13a26ae-5662-4b74-af2d-6c9e6dbeb425n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAE%3DAWBW--b8ndvgS23E%2BVDu-s1bGTuQpJ7VQJgOrT%2B2p6WFMqg%40mail.gmail.com.
