Spooky C++

A C++ program demonstrates undefined behavior that causes a permission-granting security check to fail at optimization level -O0 but pass at -O2, affecting both Clang and GCC across C++17, C++20, and C++23. The bug occurs because the code returns a `std::string_view` to a temporary string that gets destroyed, and compiler optimizations expose this memory safety issue in unpredictable ways. While humorously framed as "spooky," this illustrates how undefined behavior in C++ can produce counterintuitive results that are difficult to detect and exploit, though easily avoided through proper refactoring practices.