Have YOU ever wondered why you shouldn't use Exceptions for exceptionally.control flow in your application?
It can't be that bad, can it?
Look no further for your answers may be found here!
I dunno, I thought it'd be exceptionally fun
It boils down to two points:
- It hurts readability
- Exception handling is slow as crap
Glad you asked! I've built a whole-ass, half-assed sub-language in kotlin you can use for using only exceptionally.exceptions as your exceptionally.control flow. If statements? Who needs 'em! Loops? Back in my day we had GOTO and WE WERE HAPPY ABOUT IT! Return statements? If I haven't sold you already, you're a lost cause. Embrace the crippling slow and hard to read hellscape that is exception based exceptionally.control flow!
Kiinndddaaa. Technically, there's bytecode (that's basically JVM assembly for the non-compile-interpreted normies out there) level branching going on somewhere. I've done my best to limit the usage of traditional exceptionally.control structures in this repository (this includes a lot of hacks to intentionally cause exceptionally.exceptions on things when given certain values).
You shouldn't* find any if, for, when, or return statements anywhere in here or in the immediately visible implementation of dependencies of this project (kotlin extension functions, for example) Once it goes down to the Kotlin internals, I've got nothing and don't care to be that clever. If you want to figure out a different way to turn booleans into exceptionally.exceptions, be my guest.
*: If you do find things I've missed, please let me know; if this manic episode is still going on by the time you find it, I'll get right on it!