As of Java 8, Java does not provide Tail-Call Optimization (TCO). On researching about it, I came to know the reason which is:
in jdk classes [...] there are a number of security sensitive methods that rely on counting stack frames between jdk library code and calling code to figure out who's calling them.
However Scala, which is based on JVM has support for Tail-Call Optimisation. Scala does tail recursion optimisation at compile-time. Why can't Java use the same approach ?
PS: Not sure whether the latest version (Java 11 as of now) of Java now has TCO. Would be great if some who knows can share this also.
Note
I know TCO is at backlog and is of lower priority but want to know why can't Java make changes in compile time similar to Scala.
Java doesn't have tail call optimization for the same reason most imperative languages don't have it. Imperative loops are the preferred style of the language, and the programmer can replace tail recursion with imperative loops. (Source)
Why can't Java use the same approach ?
I can't say which approach will be used, but it's better-explained in Project Loom's proposal:
As adding the ability to manipulate call stacks to the JVM will undoubtedly be required, it is also the goal of this project to add an even lighter-weight construct that will allow unwinding the stack to some point and then invoke a method with given arguments (basically, a generalization of efficient tail-calls). We will call that feature unwind-and-invoke, or UAI. It is not the goal of this project to add an automatic tail-call optimization to the JVM.
As far as I've heard, work has not yet begun on tail calls, as Fibers and Continuations seem to currently be a higher priority.