aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/_posts/2015-07-03-std-call-once-bug.md
diff options
context:
space:
mode:
authorEgor Tensin <Egor.Tensin@gmail.com>2022-04-26 11:53:12 +0200
committerEgor Tensin <Egor.Tensin@gmail.com>2022-04-26 12:04:23 +0200
commit166e16d9d14d3d8323a90ca2444918267a3afca1 (patch)
tree870b0148c4a7c0e44bedf1c759d91becea194932 /_posts/2015-07-03-std-call-once-bug.md
parentstatic-vs: move TL;DR to top (diff)
downloadblog-166e16d9d14d3d8323a90ca2444918267a3afca1.tar.gz
blog-166e16d9d14d3d8323a90ca2444918267a3afca1.zip
shorter post excerpts
Diffstat (limited to '')
-rw-r--r--_posts/2015-07-03-std-call-once-bug.md5
1 files changed, 2 insertions, 3 deletions
diff --git a/_posts/2015-07-03-std-call-once-bug.md b/_posts/2015-07-03-std-call-once-bug.md
index 9e82b84..e4d5a82 100644
--- a/_posts/2015-07-03-std-call-once-bug.md
+++ b/_posts/2015-07-03-std-call-once-bug.md
@@ -1,9 +1,8 @@
---
title: std::call_once bug in Visual C++ 2012/2013
excerpt: >
- 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.
+ There's a nasty bug in the C++ Standard Library implementation shipped with
+ Microsoft Visual Studio 2012/2013.
category: C++
---
I've recently come across a nasty standard library bug in the implementation