Whenever the compiler refuses to compile because of an unused var:
Hey Jeff, we know the variable is unused. WE CAN SEE THE SQUIGGLE
Give me Options or give me death
Submitted 9 months ago by YIj54yALOJxEsY20eU@lemm.ee to programmer_humor@programming.dev
https://lemm.ee/pictrs/image/c60def1e-a660-49c6-b3b6-c8ccc9be913a.jpeg
Comments
bleistift2@feddit.de 9 months ago
RustyNova@lemmy.world 9 months ago
Not a go dev. Is it really preventing compilation or is it just some hardened linting rules? Most languages can prevent compile on those errors, but that seems bad if it’s not a warning
xmunk@sh.itjust.works 9 months ago
Yes, and it fucking sucks. It’s a great thing to lint for but it makes debugging such a pain - commenting out an irrelevant block to focus your debugging will sometimes break your ability to compile… it’s extremely jarring.
dbx12@programming.dev 9 months ago
Unused variable is an error which fails to compile.
YIj54yALOJxEsY20eU@lemm.ee 9 months ago
I don’t think its inherently bad but it feels jarring when the language allows you reference nill pointers. It’s so effective in its hand holding otherwise that blowing things up should not be so easy.
GarytheSnail@programming.dev 9 months ago
Yes but I’ve never found it to be that annoying.
xmunk@sh.itjust.works 9 months ago
You’ll
go fmtand you’ll like it. Go has the single easiest to Google name of any programming language. Thou shalt not question golang decisions.fl42v@lemmy.ml 9 months ago
Go has the single easiest to Google name of any programming language.
Ackchually Screenshot_20240215-004708_Mull
xmunk@sh.itjust.works 9 months ago
C is also bad - but I do think .Net takes the cake. I’m willing to give C a pass though since it existed before we had search engines… Go was specifically developed at Google so there’s no excuse.
sbv@sh.itjust.works 9 months ago
it’s like half the number of keystrokes
30p87@feddit.de 9 months ago
I’m gonna name some language “``` head -n1 /dev/random | base64 ``” so it’s easy to search
xmunk@sh.itjust.works 9 months ago
I’m a cruel person - so I’ve been contemplating naming a language
.NET
RustyNova@lemmy.world 9 months ago
Ah yes. The good old
go figure --it outmozz@mbin.grits.dev 9 months ago
I thought everyone else just did what I do -- if there's a squiggle, take away the squiggle part. If something's missing, make a blank line and then blindly bounce on the tab key until Copilot fixes it.
That's step 1, and if that doesn't work, step 2 is to actually look at what's going on and try to fix it.
frezik@midwest.social 8 months ago
I ran across an old Stackoverflow question from many years ago where someone asked a question about types and wondered if generics could solve it. There was a very high-minded, lengthy reply that Go does not have generics, because that makes the language small and clean.
Since then, Go has implemented generics. Because who the hell wants a strongly typed language without generics on this side of 2010?
xmunk@sh.itjust.works 8 months ago
I honestly only think generics made it into Go because the designers started getting embarrassed by the solution to nearly every problem being “create an empty interface”.
dejected_warp_core@lemmy.world 8 months ago
on this side of 2010?
On this side of 1990. I’m not saying C++ did this right, but it embraced the idea that maybe the compiler could do a little more for us. And every time someone fielded a new language with some traction, eventually they added generics or just used duck-typing from the start.
Scrath@lemmy.dbzer0.com 9 months ago
You bring back my bad memories of having to implement a server program in rust and all my searches ended up with about 1/3 useful results and the rest being hosting options for rust gameservers
pkill@programming.dev 8 months ago
gofumpt’s even beter, also golaegci-lint-langserver
xlash123@sh.itjust.works 8 months ago
Imagine getting segmentation faults at runtime
This post was brought to you by the Rust crew
PoolloverNathan@programming.dev 8 months ago
Neither does Haskell, and Haskell won’t waste time doing something that doesn’t matter.
anton@lemmy.blahaj.zone 8 months ago
Imagine using a linked list as your default sequential container.
Rust iterators are lazy btw.
tuto193@lemmy.world 9 months ago
As a use-rust-for-even-the-most-basic-task elitist, I laugh.
joyjoy@lemm.ee 9 months ago
panic();pkill@programming.dev 8 months ago
Here you are pkg.go.dev/github.com/samber/mo
YIj54yALOJxEsY20eU@lemm.ee 8 months ago
Thank you very much, I’m definitely going to take this for a spin! Can I ask if you or someone you know uses this?
pkill@programming.dev 8 months ago
A simple example:
func GetConfig(path string) mo.Result[*Config] { return mo.Try(func (*Config, error) { // logic to get the config }) } conf := GetConfig.OrElse(&Default config)
While it might not make much sense for a function you use just once, it can get actually pretty useful to simplify error handling like this for something you use more often.
pkill@programming.dev 8 months ago
mostly the
Resulttype.MustGetwhere you’d except a panicOrElseto pass a fallback value (can be a function with unwrapped value of the same return type, but without an error). Useful in e.g. more complex constructors where some fields might not be readily available.Eithercan for instance be useful to have arbitrary type unions in structs. I haven’t usedOptionthat much but seems similar to Rust’s.
LinearArray@programming.dev 8 months ago
Panik !!
jaxxed@lemmy.world 8 months ago
It’s not easy to discover that you passed an empty memory pointer.
xmunk@sh.itjust.works 9 months ago
Maybe I will… maybe I won’t.
ByteJunk@lemmy.world 9 months ago
I couldn’t care less about crashes, that’s an end-user problem. But do you expect me to go to sleep while that squiggly line is in my IDE??
/s just in case
YIj54yALOJxEsY20eU@lemm.ee 9 months ago
Step 1: Remove the LSP from IDE.mod Step 2: Run ‘’‘go mod tidy’‘’
kevincox@lemmy.ml 8 months ago
I mean it isn’t even just a squiggly line, the code fails to compile. Like come on, I will clean up my unused imports and variables before sending it for review, but just let me develop in peace.