> trivial to fix if it ever causes any trouble So your library exposes __foo or foo_t, a program depends on your library and some other library. Now a new sta

> trivial to fix if it ever causes any trouble So your library exposes __foo or foo_t, a program depends on your library and some other library. Now a new standard comes out and adds __foo or foo_t to the standard library, and the program upgrades to the new standard. So far everything works. Now the other library upgrades to the new standard as well and uses standard __foo or foo_t. Now the program experiences weird linker errors or runtime undefined behavior. Trivial to fix.