> And my answer demonstrates that you do not have to
Then again - "where does that `to_enum_string` come from exactly?".
Then again - "where does that `to_enum_string` come from exactly?".
How many libraries do you read the source code after installing them with the package manager?
Can you quote the C++ standard section that specifically talks about the `to_enum_string` function?
It is on the same place as left pad on ECMA 262.
First of all, the only correct way to use package managers is with validated internal repos, don't vibe install, that goes for node, and goes for C++ as well.
Second this thread was all about how code lands in one's computer.
#include "to_enum_string.h"
You don't have to understand it to use it. Even then, it's not that hard to understand, it just looks unfamiliar.