From 3627efe03bd9ec40514d1d6315bf636a4b239a6f Mon Sep 17 00:00:00 2001
From: Jason Turner <jason@emptycrate.com>
Date: Wed, 16 Mar 2016 20:14:48 -0600
Subject: [PATCH] Move away from shared_lock

It's not supported by enough standard library implementations yet
---
 include/chaiscript/chaiscript_threading.hpp | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/include/chaiscript/chaiscript_threading.hpp b/include/chaiscript/chaiscript_threading.hpp
index 126edb9..2250693 100644
--- a/include/chaiscript/chaiscript_threading.hpp
+++ b/include/chaiscript/chaiscript_threading.hpp
@@ -13,7 +13,6 @@
 #ifndef CHAISCRIPT_NO_THREADS
 #include <thread>
 #include <mutex>
-#include <shared_mutex>
 #else
 #ifndef CHAISCRIPT_NO_THREADS_WARNING
 #pragma message ("ChaiScript is compiling without thread safety.")
@@ -46,13 +45,13 @@ namespace chaiscript
         using unique_lock = std::unique_lock<T>;
 
       template<typename T>
-        using shared_lock = std::shared_lock<T>;
+        using shared_lock = std::unique_lock<T>;
 
       template<typename T>
         using lock_guard = std::lock_guard<T>;
 
 
-      using shared_mutex = std::shared_timed_mutex;
+      using shared_mutex = std::mutex;
 
       using std::mutex;