News for hackers. Stuff that matters.
Re:New in Go 1.20: wrapping multiple errors by pjmlp on Sunday December 11, 2022 @09:31AM (#33943520)
> Or just use any of the popular Go code editors/plugins which give you a "show me all implementations".

And me thinking the Go culture is against languages that tend to come with IDEs...

Re:New in Go 1.20: wrapping multiple errors by cube2222 on Sunday December 11, 2022 @09:53AM (#33943678)
Go culture, like any other, is diverse.

I prefer to use an editor/IDE and don't think it's pleasant to work with any language (including Go) without them.

Re:New in Go 1.20: wrapping multiple errors by za3faran on Sunday December 11, 2022 @03:07PM (#33946923)
Not to mention how slow it becomes in large projects
Re:New in Go 1.20: wrapping multiple errors by foldr on Sunday December 11, 2022 @09:34AM (#33943548)
You don't need an IDE to do that. More or les anything that can hook up with the Go language server will do the job.
Re:New in Go 1.20: wrapping multiple errors by pjmlp on Sunday December 11, 2022 @09:48AM (#33943642)
So somehow needing a language server to work around language design flaws is alright for Go then.
Re:New in Go 1.20: wrapping multiple errors by foldr on Sunday December 11, 2022 @11:41AM (#33944709)
Sarcasm aside, I do think it’s fair to assume that someone writing code in a modern programming language in 2022 has access to basic language-aware editor tooling. That’s the beauty of the language server. You can look up the implementations of an interface from vim, or some other minimalist development environment, if that’s your bag.
Re:New in Go 1.20: wrapping multiple errors by masklinn on Sunday December 11, 2022 @12:04PM (#33944960)
"Go is so simple you don't need an IDE to write it, unlike java"

"Well obviously you need a proper IDE to protect you from Go's fuckups"

Cool.

Re:New in Go 1.20: wrapping multiple errors by foldr on Sunday December 11, 2022 @12:40PM (#33945341)
You don’t need an IDE, as I explained in my two preceding posts in this thread. Please at least try to respond to someone who is actually making the arguments that you take yourself to be refuting.