"On windows, you need to always, always call Close() on file handles before attempting to delete them. This is easy enough to do when the deletion happens near the access like above. But when you're writing a program that touches many thousands of files in a long-lived process, it's very easy to accidentally lose track of one or more of them."
"On windows, you need to always, always call Close() on file handles before attempting to delete them. This is easy enough to do when the deletion happens near the access like above. But when you're writing a program that touches many thousands of files in a long-lived process, it's very easy to accidentally lose track of one or more of them."
Isn't that what `defer` is for?
Defer only defers to the end of the scope so, "no" if the handle is one that needs to survive the function it was opened in.
You can do this in many ways, but you can also do it like this:
Start a goroutine and use channels to communicate and coordinate reading/writing. Use defer in the goroutine.