stravant

--------------------------------------------------------------------------------
--               Batched Yield-Safe Signal Implementation                     --
-- This is a Signal class which has effectively identical behavior to a       --
-- normal RBXScriptSignal, with the only difference being a couple extra      --
-- stack frames at the bottom of the stack trace when an error is thrown.     --
-- This implementation caches runner coroutines, so the ability to yield in   --
-- the signal handlers comes at minimal extra cost over a naive signal        --
-- implementation that either always or never spawns a thread.                --
--                                                                            --
-- API:                                                                       --

evaera

1. Use descriptive and obvious names.
   • Don't use abbreviations, use full English words. player is better than plr.
   • Name things as directly as possible. wasCalled is better than hasBeenCalled. notify is better than doNotification.
   • Name booleans as if they are yes or no questions. isFirstRun is better than firstRun.
   • Name functions using verb forms: increment is better than plusOne. unzip is better than filesFromZip.
   • Name event handlers to express when they run. onClick is better than click.
   • Put statements and expressions in positive form.
     • isFlying instead of isNotFlying. late intead of notOnTime.
     • Lead with positive conditionals. Avoid if not something then ... else ... end.

• If we only care about the inverse of a variable, turn it into a positive name. missingValue instead of not hasValue.