> What nasal demons? Those that result from the pre-C++26 behavior where use of an indeterminate value is UB. > But there’s lots of room between deterministic

> What nasal demons? Those that result from the pre-C++26 behavior where use of an indeterminate value is UB. > But there’s lots of room between deterministic values and UB. That's a fair point. I do think I made a mistake in how I represented the authors' decision, as it seems the authors intentionally wanted the predictability of fixed values (italics added): > Reading an uninitialized value is never intended and a definitive sign that the code is not written correctly and needs to be fixed. At the same time, we do give this code well-defined behaviour, and if the situation has not been diagnosed, we want the program to be stable and predictable. This is what we call erroneous behaviour. > And I think the word “indeterminate” should have been reserved for that sort of behavior. Perhaps, but that'd be a departure from how the word has been/is used in the standard so there would probably be some resistance against redefining it.