Why isn’t short variable declaration allowed at package level in Go?

by

According to Ian Lance Taylor in this thread shortly after the public announcement:

At the top level, every declaration begins with a keyword. This simplifies parsing.

More Related Contents:

  1. Create a generic channel
  2. How to pipe several commands in Go?
  3. How to use a module that is outside of “GOPATH” in another module?
  4. How can I convert string to integer in golang
  5. How to dump goroutine stacktraces?
  6. Cyclic dependencies and interfaces
  7. Accessing struct fields inside a map value (without copying)
  8. Why do I get a “cannot assign” error when setting value to a struct as a value in a map? [duplicate]
  9. Can I concurrently write different slice elements
  10. Organize local code in packages using Go modules
  11. Golang Dependency Management Best Practice
  12. How can I pass a slice as a variadic input?
  13. Does Go provide REPL?
  14. How to compare if two structs, slices or maps are equal?
  15. Golang defer behavior
  16. Example for sync.WaitGroup correct?
  17. Stack vs heap allocation of structs in Go, and how they relate to garbage collection
  18. How to fix parsing go.mod module declares its path as “x” but was required as “y”
  19. What is the meaning of “dot parenthesis” syntax? [duplicate]
  20. What is the idiomatic Go equivalent of C’s ternary operator?
  21. Can I construct a slice of a generic type with different type parameters?
  22. Why would I make() or new()?
  23. How to import local packages in go?
  24. How to implement generic interfaces?
  25. How to compare Go errors
  26. How do you statically link a c library in go using cgo?
  27. Go struct tags with underscore before function names
  28. calling command with some arguments works but not with others but works from console
  29. Do buffered channels maintain order?
  30. What do “value semantics’” and “pointer semantics” mean in Go?

Leave a Comment