Thank you.

Thanks for the link

The performant comment makes a lot of sense. Can we spell out what the other assumptions are so I can get a better understanding?

This is a fair assessment. This is really just a "harder" take on the same problem that accounts for some very common edge-cases. Personally, I've seen enough "Code Golf" 30-character solutions to these 7 kyu problems and wanted to provide a different perspective. We're all just here to learn, and I believe this solution provides an opportunity to learn that isn't as common here on CodeWars.

It's bad. The programmer assumes things which you should never do. This solution is vastly less performant because of that. It should only be transfored to this when the actual implementation calls for this change, never sooner.

Ah, that makes sense. I'll have to declare those in the future. Thank you for explaining :)

thanks for the comments explaining what you were doing. Was helpful in learning

Seems reasonable. It's reusable, and well named.

Nice clean solution! Thanks!

Thanks for adding the code comments. Very helpful when trying to figure out the best practices for this particular solution!