Last active
March 30, 2024 08:03
-
-
Save razimantv/1b33d4a090a5bc9ed94928012b37c3f0 to your computer and use it in GitHub Desktop.
Next step: tail-recursion optimization
Cool hack, but a-huy is right: a naked except clause? Tsk tsk..
Can't wait for proper recursion now!
👍
🤘
a custom exception is not needed, the exception problem can be fixed by reducing the scope of the try block and using some messy branching or a tidy little goto.
I think you can pass __next_arg via exception params instead of stackify object state.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You might want to define a custom Exception class for this - it looks like the current implementation will confuse KeyboardInterrupt and unrelated functional exceptions as an attempt to recurse.