aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/_posts/2015-07-03-std-call-once-bug-in-visual-studio-2012-2013.md
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--_posts/2015-07-03-std-call-once-bug-in-visual-studio-2012-2013.md7
1 files changed, 1 insertions, 6 deletions
diff --git a/_posts/2015-07-03-std-call-once-bug-in-visual-studio-2012-2013.md b/_posts/2015-07-03-std-call-once-bug-in-visual-studio-2012-2013.md
index 701c323..0fd6c30 100644
--- a/_posts/2015-07-03-std-call-once-bug-in-visual-studio-2012-2013.md
+++ b/_posts/2015-07-03-std-call-once-bug-in-visual-studio-2012-2013.md
@@ -2,15 +2,10 @@
title: std::call_once bug in Visual Studio 2012/2013
layout: post
excerpt: >
- In this post I will describe a neat bug I've stumbled upon in the C++
+ In this post I will describe a nasty bug I've stumbled upon in the C++
Standard Library implementation shipped with Microsoft Visual Studio
2012/2013.
---
-{{ page.excerpt }}
-
-Introduction
-------------
-
I've recently come across a nasty standard library bug in the implementation
shipped with Microsoft Visual Studio 2012/2013.
[StackOverflow was of no help], so I had to somehow report the bug to the