It's actually possible to implement calling in such a way that TCO is compatible with Java's security architecture (or at least as it was back in the late 90s w

It's actually possible to implement calling in such a way that TCO is compatible with Java's security architecture (or at least as it was back in the late 90s when I cared about this). IIRC you'd have a finite state machine along with your calls, which would transit when you're making a tail call of the sort which would matter to the security checks. In other words, the amount of security state needed by a tail-call chain was bounded, if you implemented the spec in a tail-call conscious way. I thought stack inspection was a bad idea anyway, but you could implement it together with TCO. [edited because truncated by misclick]