Discussion
Loading...

Post

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Anders Eknert
@anderseknert@swecyb.com  ·  activity timestamp last week

From the #golang docs on naming packages. Which is good advice of course. But whoever named Go stdlib packages like "path", "list", "fs", "maps", "flag", "hash", "strings", "iter", "url", "mail", "user", "metrics", "scanner", "sort", "slices", "template", "unique" was clearly not having any of that.

Screenshot of a paragraph in Go's documentation saying "Don’t steal good names from the user. Avoid giving a package a name that is commonly used in client code. For example, the buffered I/O package is called bufio, not buf, since buf is a good variable name for a buffer."
Screenshot of a paragraph in Go's documentation saying "Don’t steal good names from the user. Avoid giving a package a name that is commonly used in client code. For example, the buffered I/O package is called bufio, not buf, since buf is a good variable name for a buffer."
Screenshot of a paragraph in Go's documentation saying "Don’t steal good names from the user. Avoid giving a package a name that is commonly used in client code. For example, the buffered I/O package is called bufio, not buf, since buf is a good variable name for a buffer."
  • Copy link
  • Flag this post
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.0-rc.2.6 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct