If you’re working in a truly thunky language, there is a nifty little solution that helps avoid repeating successor chain implementations. Be warned! This solution is so cool, you may wind up with a serious case of code-envy on your hands.
You'll need an account to access this thunky content. Sign-up for a most compendious plan now!
If you previously created an account, login with one of:
Or a password: