I think people don’t understand very well what is happening there… Here is probably best example in pseudo code:
When you call function TestShortCircuit in C++ your output log will be:
When you construct same condition using blueprint node your log will be:
because blueprint is probably not wise enough to detect that condition can never be true when first function (A) returned false.
I belive it is “by design” because Epic doesn’t like forcing people to take care of order of input pins for pure functions… But yes, some AND node with Short Circuit implemented will make conditions nicer and life will be easier!