>> Your suggestion of pushing it into a separate function (which
>> presumably would just mean using return instead of break to
>> terminate the code block) strikes me as worth considering in general
>> but a bad idea in this case; there are too many things that would
>> have to be passed down to t
On Sat, Oct 01, 2022 at 07:59:23PM -0400, Mouse wrote:
>
> usual approach to such things. Your suggestion of pushing it into a
> separate function (which presumably would just mean using return
> instead of break to terminate the code block) strikes me as worth
> considering in general but a bad i
