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
{{ message }}
This repository was archived by the owner on Feb 1, 2025. It is now read-only.
I was reading through the runtime today and noticed the use of try/catch in runtime.async and invoke on two places. This will lead to deoptimizations and as they are core prices of functionality they are crucial for good performance. This can be fairly easily be avoided and I see two primary ways of doing the, either add a helper function like this:
Or break out the mentioned sections of code into their own function to lessen the effect. I suggest the first, but it might be good to break out some of the code from invoke since it is currently ~110 lines long. What do you think about this? Which way do you think is best?
I was reading through the runtime today and noticed the use of try/catch in runtime.async and invoke on two places. This will lead to deoptimizations and as they are core prices of functionality they are crucial for good performance. This can be fairly easily be avoided and I see two primary ways of doing the, either add a helper function like this:
Or break out the mentioned sections of code into their own function to lessen the effect. I suggest the first, but it might be good to break out some of the code from
invokesince it is currently ~110 lines long. What do you think about this? Which way do you think is best?