std::string_view causes dangling references when using with std::vector in C++17
I'm building a feature where Hey everyone, I'm running into an issue that's driving me crazy. I'm sure I'm missing something obvious here, but I'm working with an scenario with `std::string_view` where it seems to be causing dangling references when used alongside `std::vector` in my C++17 project. I have a vector of strings, and I'm trying to create string views from it for efficient read access. However, when the vector is modified (like when I add or remove elements), the string views point to invalidated memory. Here's a simplified version of my code: ```cpp #include <iostream> #include <string> #include <string_view> #include <vector> int main() { std::vector<std::string> myStrings = {"Hello", "World", "Test"}; std::vector<std::string_view> myViews; for (const auto& str : myStrings) { myViews.emplace_back(str); } myStrings.push_back("New String"); // This seems to invalidate views for (const auto& view : myViews) { std::cout << view << std::endl; // Unexpected behavior here } } ``` When I run this code, I expect to see all my views printed correctly, but when I modify `myStrings`, it looks like the views become invalid and print garbage or lead to undefined behavior. I thought `std::string_view` was designed to be lightweight and efficient without owning the string data, but I didn't realize it could lead to dangling references when the original string container changes. I've read up on the lifetime of objects in C++, but I'm still confused about how to properly manage `std::string_view` with containers that can change size dynamically. Is there a recommended approach to handle this situation without losing the performance benefits of `std::string_view`? Should I be storing the actual strings instead of views, or is there a different pattern I should follow? Any insights would be greatly appreciated! This is part of a larger service I'm building. My development environment is Linux. What am I doing wrong? What am I doing wrong? For reference, this is a production REST API. Any ideas what could be causing this?