Every LLM hallucinates that std:vector deletes elements in LIFO order (am17an.bearblog.dev)

A recent exploration revealed that leading language models (LLMs) incorrectly assume that the C++ `std::vector` container deletes elements in a Last-In-First-Out (LIFO) order. This misunderstanding surfaced when a developer was advised by multiple LLMs to use `std::vector` for LIFO deletion, prompting further investigation. A simple C++ program demonstrated that `std::vector` actually destructs elements from front to back, contradicting the LLMs' assertions. This has implications for developers relying on AI for accurate programming advice. The confusion likely stems from a mix-up between the destruction order of `std::vector` elements and the LIFO order of class member destructors, a point the LLMs acknowledged as being contentious and implementation-dependent in the C++ Standard. By bringing this issue to light, the author hopes to facilitate corrections in future LLM iterations, suggesting that it could take under six months to address. This unfolds a significant lesson about the reliability of AI guidance in programming, highlighting the need for critical evaluation of AI-generated advice, especially concerning nuanced technical details.