eta
eta copied to clipboard
Nested trampolines should be no-ops
What happens when you trampoline twice in the same "thread" of computation? The nested trampoline will restart the tail call counter and start a fresh trampoline. This is not desirable. Instead, we should make it a no-op (just evaluate the closure). This should be a couple line fix, will detail more for anyone interesting in implementing this.
As discussed in #901