Why does golang compiler think the variable is declared but not used?

by

The err inside the for is shadowing the err outside the for, and it’s not being used (the one inside the for). This happens because you are using the short variable declaration (with the := operator) which declares a new err variable that shadows the one declared outside the for.

More Related Contents:

  1. Pre-processor directive in Go like in C [duplicate]
  2. Golang ascending order
  3. Convert map values to plain strings without brackets? [closed]
  4. What are the use(s) for tags in Go?
  5. is there a way to create an instance of a struct from a string?
  6. How to avoid annoying error “declared and not used”
  7. Splitting client/server code
  8. Collect values in order, each containing a map
  9. Pass method argument to function
  10. How safe are Golang maps for concurrent Read/Write operations?
  11. How to reduce compiled file size?
  12. Why are interfaces needed in Golang?
  13. In Go is naming the receiver variable ‘self’ misleading or good practice?
  14. Is there a way to do repetitive tasks at intervals?
  15. How do I configure go command to use a proxy?
  16. Golang. What to use? http.ServeFile(..) or http.FileServer(..)?
  17. Custom type passed to function as a parameter
  18. What do three dots “./…” mean in Go command line invocations?
  19. Struct in for loop initializer
  20. How can I “go run” a project with multiple files in the main package?
  21. Is it possible to have nested templates in Go using the standard library?
  22. How can I instantiate a non-nil pointer of type argument with generic Go?
  23. Making golang Gorilla CORS handler work
  24. When do you embed mutex in struct in Go?
  25. How to embed file for later parsing execution use
  26. How to clone a structure with unexported field?
  27. Closing channel of unknown length
  28. Testing a gRPC service
  29. Force priority of go select statement
  30. Go exec.Command() – run command which contains pipe

Leave a Comment