Go for Bash Programmers – Part II: CLI Tools

(github.com)

113 points | by reisinge 2 days ago ago

4 comments

  • everybodyknows 18 hours ago ago

    > We named the package hello_test instead of hello. This is possible and it allows for writing tests that use only the public API (identifiers starting with a capital letter) of the tested package as a real user would.

    Would be good to highlight here that *_test packages are the sole exception from Go's standard rule of one-package-only per source directory -- special cases being always an unfortunate additional heightening of the beginner's learning curve.

    • ttz 8 hours ago ago

      You can also include

      package main

      files in a non-main package directory (usually sed when implementing go generate)

  • mrbluecoat 18 hours ago ago

    I really like this style of showing steps that would be logical for those new to Go even if they're wrong then showing why it didn't work and walking through the fix. Nice linear progression of real-world learning.

  • pentaphobe 18 hours ago ago

    Nice! You packed in so many things which are often drip fed, and take folk a while to find

    Kudos