<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>GoLang on Saleem Ansari</title>
    <link>/tags/golang/</link>
    <description>Recent content in GoLang on Saleem Ansari</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>(c) 2024 Saleem Ansari</copyright>
    <lastBuildDate>Tue, 15 Dec 2015 04:36:55 +0530</lastBuildDate>
    <atom:link href="/tags/golang/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go Garbage Collector</title>
      <link>/2015/12/15/go-garbage-collector/</link>
      <pubDate>Tue, 15 Dec 2015 04:36:55 +0530</pubDate>
      <guid>/2015/12/15/go-garbage-collector/</guid>
      <description>After trying Go for the first time recently, I am amazed with how fast the programs compile. The compiled code ends up being in machine code, and no intermediate virtual machine is required. However, there is one piece that is present in each executable i.e. the garbage collector - GC.&#xA;But, how does GC work in Go? How tunable is it? For now this is what I have found:&#xA;On the topic of performance, keep in mind that Go gives the programmer considerable control over memory layout and allocation, much more than is typical in garbage-collected languages.</description>
    </item>
  </channel>
</rss>
