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
This project is using a lot of bleeding edge WebAssembly stuff so it does not have good compatibility with old browsers.
I am mostly interested in supporting evergreen browsers (the latest versions) but I would like to support older ones if it's possible without too much pain.
I would also like to use top-level await which pushes Firefox to 89, but I am not sure which tooling that might break so I'll hold off on it for now. With top-level await, we can remove the necessity for the load() function and let people call new Prolog() as soon as the import resolves.
The text was updated successfully, but these errors were encountered:
Also worth mentioning, we use FinalizationRegistry if we can. This is from Firefox 79. If we start using top-level await we can remove the compatibility check here.
This functionality isn't strictly necessary but it can help clean up memory from leaked queries.
This project is using a lot of bleeding edge WebAssembly stuff so it does not have good compatibility with old browsers.
I am mostly interested in supporting evergreen browsers (the latest versions) but I would like to support older ones if it's possible without too much pain.
Current situation:
I would also like to use top-level await which pushes Firefox to 89, but I am not sure which tooling that might break so I'll hold off on it for now. With top-level await, we can remove the necessity for the
load()
function and let people callnew Prolog()
as soon as the import resolves.The text was updated successfully, but these errors were encountered: