Hello, Detecting all unclosed Closers in any case sounds a bit undecidable to me (sounds like the halting problem). But detecting some of them would be feasible.
Le jeudi 28 décembre 2017 17:58:06 UTC+1, Brian Sorahan a écrit : > > That seems like a decent affirmation! Thanks. > > On Wednesday, December 20, 2017 at 9:42:55 AM UTC-6, Howard C. Shaw III > wrote: >> >> In the absence of an affirmative, I'll just say that I did a search of my >> own. >> >> This site: >> https://github.com/mre/awesome-static-analysis >> lists a bunch of static analysis tools for go. >> >> https://github.com/alecthomas/gometalinter has another list, and will >> run them for you. They have binary packages now at >> https://github.com/alecthomas/gometalinter/releases that include the >> linters they can run. >> >> I wrote a minimal program that has the condition of opening an os.File, >> which is an os.Closer, and not explicitly closing it. None of them >> complained about this minimal program, so it is reasonable to assume that >> none of the static analysis tools on the gometalinter list check for that. >> >> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
