sipkab

3 ms·

1. 1.▲
   by sipkab 6y ago

   This optimization is simply a goto to the start of the function, and reassignment of the arguments. It doesn't prevent exception handling in any way. It doesn't interfere with debugging tools. The point is that when your program t
2. 2.▲
   by sipkab 6y ago

   It works on bytecode, so yes, it should apply to all JVM based languages. (Though I haven't done tests for them)
3. 3.▲
   by sipkab 6y ago

   Definitely not by default. This optimization messes with the stack trace, so if you throw an exception in one of the recursively called methods, it will only show up only once in the stack trace. This may very well cause confusion in cases
4. 4.▲
   Show HN: Tail Recursion Optimization for the JVM(github.com)

   107 points by sipkab 6y ago|38 comments
5. 5.▲
   by sipkab 7y ago

   Hey HN! Over the past few years, I've developed saker.build and decided to open-source it. It supports all features that a modern build system should, it's language idependent, performs fast incremental and clean builds, allows di
6. 6.▲
   Show HN: Saker.build – A modern, incremental and distributed build system(github.com)

   2 points by sipkab 7y ago|1 comments