Handling exceptions should never be a question in any library. However, because we're generating a lot, we can actually avoid the performance overhead if so required. So do we give the user that option? If we provide an option to generate try/catch around command runs, then, really, if they desire they can remove that and thus remove the overhead.
Handling exceptions should never be a question in any library. However, because we're generating a lot, we can actually avoid the performance overhead if so required. So do we give the user that option? If we provide an option to generate try/catch around command runs, then, really, if they desire they can remove that and thus remove the overhead.