<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Go on Andrew Chilton</title>
    <link>https://chilts.org/categories/go/</link>
    <description>Recent content in Go on Andrew Chilton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-nz</language>
    <managingEditor>andychilton@gmail.com (Andrew Chilton)</managingEditor>
    <webMaster>andychilton@gmail.com (Andrew Chilton)</webMaster>
    <lastBuildDate>Mon, 12 Jun 2017 23:13:22 +0000</lastBuildDate>
    
	<atom:link href="https://chilts.org/categories/go/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Cancelling Multiple Goroutines</title>
      <link>https://chilts.org/cancelling-multiple-goroutes/</link>
      <pubDate>Mon, 12 Jun 2017 23:13:22 +0000</pubDate>
      <author>andychilton@gmail.com (Andrew Chilton)</author>
      <guid>https://chilts.org/cancelling-multiple-goroutes/</guid>
      <description>Cancelling Multiple Goroutines When Go was first released, there was a way to do some things in concurrency. As time has gone on, various things have changed. The Context package for one thing. :)
This article doesn&amp;rsquo;t go into all of the ways of doing concurrency but will focus on one problem and take you through a few different solutions so you can see how things have evolved.
The Problem The problem I&amp;rsquo;d like to address here is being able to cancel multiple goroutines.</description>
    </item>
    
    <item>
      <title>Creating a Better ReadMe for GoLang Packages</title>
      <link>https://chilts.org/readme-minimum-info-needed-for-your-golang-library/</link>
      <pubDate>Tue, 10 Jan 2017 11:25:58 +0000</pubDate>
      <author>andychilton@gmail.com (Andrew Chilton)</author>
      <guid>https://chilts.org/readme-minimum-info-needed-for-your-golang-library/</guid>
      <description>We&amp;rsquo;re lucky in the Go community in that we decided to converge around simple but very useful tools early on in the ecosystem. go fmt is always looked at as one of the most important tools for your average Go programmer. Many other tools have also risen to prominence and become really, really useful. We have it good - though perhaps you make your own luck.
However some things can be better.</description>
    </item>
    
  </channel>
</rss>