https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88662
--- Comment #12 from gnzlbg <gonzalobg88 at gmail dot com> --- > I disagree. Once it's documented, people will rely on it and scream if it > changes. Caveats about something maybe changing in future don't help. If it's > documented to behave one way today, people will depend on that. That's fair. > It seems you already know what the behaviour is today If you tell me that my thoughts about how this currently works are correct then that documents current behavior, and my code will depend on this. > so how would documenting it but saying "this might change tomorrow!" help > you? It tells you nothign you don't already know. If this was documented somewhere for a particular version of GCC, when my code is compiled with that particular GCC version, I could check inputs for invalid _Bools in my programs and abort reliably without triggering undefined behavior. If this is not documented anywhere, I can at best write code that "maybe aborts or maybe has undefined behavior". I find the difference very significant.
