ipmonkey
Re:Expectations for generics in Go 1.18
on Sunday October 31, 2021 @01:39PM (#29058718)
Early return is definitely a part of the problem. One thing you could do with generics is create option/result wrappers that would work with any code and hack together a try/early return solution using panic/recover, but you'd offend the Go community, and at that point you might as well just use Rust.
Re:Expectations for generics in Go 1.18
on Sunday October 31, 2021 @01:31PM (#29058641)
vim user here. Most of us are running the same linters and language servers as every other major editor, which does a pretty good job catching stuff like this. Modern vim is really only a C core with a web of JS, Python, Lua, and vimscript using the exact same third party solutions for every other part of an "IDE". emacs is probably similar, but no personal experience with that.