From 76832333ab3a2121727ddedf4fc7f03ddc883e69 Mon Sep 17 00:00:00 2001 From: Egor Tensin Date: Tue, 8 Mar 2016 00:13:52 +0300 Subject: std::call_once: add a complete code sample --- _posts/2015-07-03-std-call-once-bug-in-visual-studio-2012-2013.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to '_posts/2015-07-03-std-call-once-bug-in-visual-studio-2012-2013.md') 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 d4e89a8..a079af0 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 @@ -279,6 +279,10 @@ So it appears that the implementation of `std::call_once` shipped with Visual Studio 2012/2013 relies on some kind of a global lock, which causes even the simple example above to misbehave. +The complete code sample to demonstrate the misbehaviour described above can be +found at +[https://github.com/egor-tensin/cpp_tips/tree/gh-pages/src/std_call_once_bug_in_visual_studio_2012_2013](https://github.com/egor-tensin/cpp_tips/tree/gh-pages/src/std_call_once_bug_in_visual_studio_2012_2013). + ## Resolution So, since I couldn't submit the bug via Visual Studio's -- cgit v1.2.3