From 5b782a783a3d8549dbeb6c89ce75b87e99d8aec0 Mon Sep 17 00:00:00 2001
From: rparanjpe <rparanjpe@teslamotors.com>
Date: Tue, 8 Dec 2015 23:31:58 -0800
Subject: [PATCH] Use a std::vector in place of stxxl:vector for the names list

-For large datasets with very many unique names, stxxl::vector can corrupt
 data. Technically, we should only be using stxxl:vectors with POD. Other
 types might lead to strange/unpredictable behavior as we noticed here.
-See http://algo2.iti.kit.edu/dementiev/stxxl/trunk/FAQ.html
---
 extractor/extraction_containers.hpp | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/extractor/extraction_containers.hpp b/extractor/extraction_containers.hpp
index 09a5ef189..ab09664a6 100644
--- a/extractor/extraction_containers.hpp
+++ b/extractor/extraction_containers.hpp
@@ -64,14 +64,13 @@ class ExtractionContainers
     using STXXLNodeIDVector = stxxl::vector<OSMNodeID>;
     using STXXLNodeVector = stxxl::vector<ExternalMemoryNode>;
     using STXXLEdgeVector = stxxl::vector<InternalExtractorEdge>;
-    using STXXLStringVector = stxxl::vector<std::string>;
     using STXXLRestrictionsVector = stxxl::vector<InputRestrictionContainer>;
     using STXXLWayIDStartEndVector = stxxl::vector<FirstAndLastSegmentOfWay>;
 
     STXXLNodeIDVector used_node_id_list;
     STXXLNodeVector all_nodes_list;
     STXXLEdgeVector all_edges_list;
-    STXXLStringVector name_list;
+    std::vector<std::string> name_list;
     STXXLRestrictionsVector restrictions_list;
     STXXLWayIDStartEndVector way_start_end_id_list;
     std::unordered_map<OSMNodeID, NodeID> external_to_internal_node_id_map;