VerifyAndClearExpectations - Setting expectations after code that exercises the mock has undefined behavior?

[DomXC]

Hello, as I have seen usage of Mock::VerifyAndClearExpectations in a codebase, where the expectations are set after the Mock::VerifyAndClearExpectations call, even in the [googlemock]

googletest/googlemock/test/gmock-spec-builders_test.cc

Lines 2276 to 2291 in 35b75a2

	TEST(VerifyAndClearExpectationsTest, CanCallManyTimes) {
	MockB b;
	EXPECT_CALL(b, DoB());
	b.DoB();
	Mock::VerifyAndClearExpectations(&b);
	EXPECT_CALL(b, DoB(_)).WillOnce(Return(1));
	b.DoB(1);
	Mock::VerifyAndClearExpectations(&b);
	Mock::VerifyAndClearExpectations(&b);
	// There should be no expectations on the methods now, so we can
	// freely call them.
	EXPECT_EQ(0, b.DoB());
	EXPECT_EQ(0, b.DoB(1));
	}

test (lines 2280 and 2282, my question is: causes really the usage as above - call VerifyAndClearExpectations, using EXPECT_CALL - undefined behavior on the mock as states int the documentation?

https://google.github.io/googletest/gmock_cook_book.html#forcing-a-verification:
"Do not set new expectations after verifying and clearing a mock after its use. Setting expectations after code that exercises the mock has undefined behavior."

Thank you.