{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"go podcast()","title":"062: Your Go linters don't know how to fix your code","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/ebdd20e7\"></iframe>","width":"100%","height":180,"duration":1229,"description":"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","thumbnail_url":"https://img.transistorcdn.com/jb5WMSQZD13ocEars69kFf1u9yukuL4DkSvOb7k0bTo/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzI3MjkyLzE2NDE1/NjU2MDgtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}