2 ms·
The problem with stack-backtraces and TCO has been well known for a long while (early 80s?) and it's indeed a serious issue. It's also related to what I've rea
by hga 16y ago
The problem with stack-backtraces and TCO has been well known for a long while (early 80s?) and it's indeed a serious issue.
It's also related to what I've read about the delay in adding TCO to JVMs: by its very nature it rewrites the stack, and confirming the safety and security of that (which a serious JVM is required to do) is not entirely trivial.
It was considered for Java 7 and will hopefully get into Hotspot someday.