<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>algorithms on Neven Miculinić</title>
    <link>https://nmiculinic.com/tags/algorithms/</link>
    <description>Recent content in algorithms on Neven Miculinić</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>neven.miculinic@gmail.com (Neven Miculinić)</managingEditor>
    <webMaster>neven.miculinic@gmail.com (Neven Miculinić)</webMaster>
    <lastBuildDate>Tue, 29 Jan 2019 10:00:00 +0200</lastBuildDate><atom:link href="https://nmiculinic.com/tags/algorithms/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Golang race detection</title>
      <link>https://nmiculinic.com/post/2019-golang-race-detection/</link>
      <pubDate>Tue, 29 Jan 2019 10:00:00 +0200</pubDate>
      <author>neven.miculinic@gmail.com (Neven Miculinić)</author>
      <guid>https://nmiculinic.com/post/2019-golang-race-detection/</guid>
      <description>Race conditions are pretty nasty bugs. Hard to trace, reproduce and isolate; often occurring under unusual circumstances and often lead to hard to debug issues. Thus it&amp;rsquo;s best to prevent &amp;amp; detect them early. Thankfully, there&amp;rsquo;s a production-ready algorithm to tackle the challenge - ThreadSanitizer v2, a battle proven library for compiler support in Go, Rust, C &amp;amp; C++.
First, let&amp;rsquo;s display a typical race condition. We have a simple global count variable:</description>
    </item>
    
  </channel>
</rss>
