062: Your Go linters don't know how to fix your code

https://is1-ssl.mzstatic.com/image/thumb/Podcasts221/v4/2f/b3/4c/2fb34c4f-a5af-04d5-650c-82d11137c9d9/mza_2777455806714113286.jpg/600x600bb.jpg

go podcast()

Dominic St-Pierre

66 episodes

15 hours ago

15 minutes news, tips, and tricks on the Go programming language.

All content for go podcast() is the property of Dominic St-Pierre and is served directly from their servers with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.

15 minutes news, tips, and tricks on the Go programming language.

Technology

Education,

How To

062: Your Go linters don't know how to fix your code

go podcast()

20 minutes

1 month ago

062: Your Go linters don't know how to fix your code

One university published attracted my attention, because it was on Go, it's titled: "Assessing Golang Static Analysis Tools on Real-World Issues".
Do you find your static analysis and linters tools could be more helpful when reporting issues?
I'm mixed feeling really, I think that they're pretty damn good. Tools can always improve for sure, not sure if we will need the help of LLMs to mix static analysis checks and LLM analysis / proposed fixes, maybe that will be the next step for those tools.

Links:

Paper's link