Incidentally, this is one of the central points of the Go article that keeps getting posted to HN and causing a flamewar each and every time from
@fasterthanlime; Go reduces complexity and makes things "simple" by just making it your/someone else's problem.
And it's absolutely not any better in terms of workability or final product.
Hey Mastodon! I'm Nora, I run a jewelry shop, and I used to rely on Twitter to find customers. I could really use your help sharing this post so I can find them here. Thanks!
#handmade #handmadejewelry #art #artistsonmastodon #artistsofmastodon #jewelry #glass #fusedglass #sellingonmastodon #smallbusiness #pride #pridejewelry #fedigiftshop
Meet Om-Nom the planet eater! He's carrot cake, spice buttercream, and mostly covered in modeling chocolate. The planets are lemon rice krispies treats covered in modeling chocolate.
@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
Trans woman, bisexual, someone's fiancée, forever a programmer, poly, and former total mess
Avatar by mavica