-
Kevin Modzelewski authored
It used to get away with telling other functions that it had already guarded its args, since it could rely on the fact that it could only get called through the path in runtimeCallInternal that would guard the args. Now that it can be called through the tpp_call fastpath (which maybe should just guard the args), it has to guard them itself.
f67fc890