3 ms·
Yeah, but we usually know what "undefined behaviour" actually means in practice. In programming languages, we can just go check what the particular compiler we'
by derefr 8y ago
Yeah, but we usually know what "undefined behaviour" actually means in practice. In programming languages, we can just go check what the particular compiler we're using spits out when you do something stupid.
It might not generalize to any other compiler—and that's the reason you don't try to build anything predicated on any particular assumption about the behavior—but you can still know it for a particular context.
And, in fact, often there are conventions in compiler-writing that mean that every compiler basically does the same thing in response to certain UB code. (Like optimizing away always-false branches, for example.)
So, by analogy: there are a limited number of autopilot AI programs in existence. Of those concrete implementations, is there anything they would be predicted to do in response to this event they're not coded for? What would it look like to them—what branch would they take without an explicit branch for "ejected"—and how would they react to being in that branch?