.Close
method GO-S2307398 if err != nil {
399 return err
400 }
401 defer f.Close()402
403 resp, err := r.getResponse()
404 if err != nil {
382 if resp.Body == nil {
383 return nil, nil
384 }
385 defer resp.Body.Close()386 data, err := io.ReadAll(resp.Body)
387 if err != nil {
388 return nil, err
398 if err != nil {
399 return err
400 }
401 defer f.Close()402
403 resp, err := r.getResponse()
404 if err != nil {
407 if resp.Body == nil {
408 return nil
409 }
410 defer resp.Body.Close()411 _, err = io.Copy(f, resp.Body)
412 return err
413}
Calling Close()
method may return an error, and ignoring the same
might result in a data loss. This is similar to many more Close
methods.
For example, on POSIX systems, os.Close
uses the close
system call underneath,
which may return an EIO
:
A previously-uncommitted write(2) encountered an input/output error.
This means that the data written by os.Write
hasn't been written to the disk,
which results in a data loss. It is recommended to handle the error returned
by the os.Close
call or call os.Sync
if available to force the OS to write
the data to the disk.
package main
import (
"fmt"
"os"
)
func foo() error {
f, err := os.Create("/tmp/test.txt")
if err != nil {
return err
}
defer f.Close()
return fmt.Fprint(f, "Hello World")
}
package main
import (
"fmt"
"os"
)
func foo() error {
f, err := os.Create("/tmp/test.txt")
if err != nil {
return err
}
err = fmt.Fprint(f, "Hello World")
if err != nil {
return err
}
return f.Close()
}
package main
import (
"fmt"
"os"
)
func foo() error {
f, err := os.Create("/tmp/test.txt")
if err != nil {
return err
}
defer f.Close()
err = fmt.Fprint(f, "Hello World")
if err != nil {
return err
}
return f.Sync()
}