Skip to content

Instantly share code, notes, and snippets.

@razimantv
Last active December 26, 2021 16:56
Embed
What would you like to do?
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@gauthamzz
Copy link

👍

@a-huy
Copy link

a-huy commented Feb 27, 2018

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.

@progval
Copy link

progval commented Feb 28, 2018

Next step: tail-recursion optimization

@petiepooo
Copy link

Cool hack, but a-huy is right: a naked except clause? Tsk tsk..

@tchoutri
Copy link

Can't wait for proper recursion now!

@LukeB42
Copy link

LukeB42 commented Feb 28, 2018

👍

@Aristarhys
Copy link

🤘

@jasen-b
Copy link

jasen-b commented Feb 28, 2018

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.

@skliarpawlo
Copy link

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