From a4d6302dabf33f0ebbbfb398e7157196d81a7faa Mon Sep 17 00:00:00 2001
From: "Dirk-Jan C. Binnema" <djcb@djcbsoftware.nl>
Date: Sat, 15 Aug 2020 10:36:10 +0300
Subject: [PATCH] mu-sexp: use std::vector instead of std::deque

Using deque gives compilation errors when compiling on
MacOS/clang (where it defaults to libc++ rather than gcc's libstdc++)

```
 #include <deque>
 struct Foo { std::deque<Foo> foos; };
 int  main() { Foo foo; }
```

So, let's use a vector instead; this is a drop-in replacement here, but
unfortunately in some future code...
---
 lib/utils/mu-sexp.hh | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lib/utils/mu-sexp.hh b/lib/utils/mu-sexp.hh
index 847eea70..f0aa27db 100644
--- a/lib/utils/mu-sexp.hh
+++ b/lib/utils/mu-sexp.hh
@@ -24,7 +24,6 @@
 #include <iterator>
 #include <string>
 #include <vector>
-#include <deque>
 #include <type_traits>
 
 #include "utils/mu-utils.hh"
@@ -49,8 +48,9 @@ struct Sexp {
          */
         Sexp():type_{Type::Empty}{}
 
-        /// Underlying data type for list
-        using Seq = std::deque<Sexp>;
+        // Underlying data type for list; we'd like to use std::dequeu here,
+        // but that does not compile with libc++ (it does with libstdc++)
+        using Seq = std::vector<Sexp>;
 
         /**
          * Make a sexp out of an s-expression string.