You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: