Did you solve/workaround the safari JIT issue in InstrumentAsyncContext? #4258
jzhan-canva
started this conversation in
General
Replies: 1 comment
-
|
Yes. It was a very weak signal, so I'm not absolutely certain, but I'm pretty sure the refactoring where we have our runtime function return a function factory made that bug impossible. That said, I don't believe we've actually opensourced the runtime part of AsyncContext, so I'm not sure how useful any of this would be for anyone else. I do have plans to opensource it hopefully soon-ish. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @shicks and anyone works on InstrumentAsyncContext
OOC, I see the commit history for InstrumentAsyncContext file that you changed the generated pattern twice to work around the webkit issue. And recently you removed the compiler option. Did you solve the webkit JIT issue?
Beta Was this translation helpful? Give feedback.
All reactions