-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TheOneric] Enable strict mode in js #46
base: master
Are you sure you want to change the base?
Conversation
This doesn't seem to add "use strict;" to workers - UPD: |
|
3252587
to
2fdc2a6
Compare
2fdc2a6
to
bab2a72
Compare
ab34008
to
5ba02cb
Compare
This will make some types of bugs easier to detect and avoid accidental additions of code not working inside Modules, which always use strict mode. Performance measurements show no relevant performance difference between strict and non-strict mode, so this won't cause regressions in this regard. Cherry-picked from: libass@c8f02d6
It turns out an optimizer pass of emscripten turned `"use strict";` into `null;`, which was fixed with emscripten 3.1.24
EVAL_CTORS now errors when used without WASM, previosuly it was likely just silently disabled. Thus, only set it when linking with WASM. Cherry-picked from: libass@45a05db
There's now a new warning when closure isn't set explicitly for non-WASM builds. Currently, there are errors concerning redeclaration of the variable screen with closure enabled, so explicitly disable it. For the future, we probably want to remove the redeclaration and enable closure. Cherry-picked from: libass@45a05db
`calledMain` global variable was removed from the JS runtime in emscripten 3.1.17
5ba02cb
to
baa99fa
Compare
Pulling from the upstream.
Original author: TheOneric
libass#143