-
Notifications
You must be signed in to change notification settings - Fork 17.3k
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
misc/wasm: wasm_exec.js does not enable strict mode #47116
Labels
arch-wasm
WebAssembly issues
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Comments
seankhliao
added
arch-wasm
WebAssembly issues
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
labels
Jul 12, 2021
Strict mode should probably be fine. 👍 |
Can I try to make changes for this issue following the guideline? |
Sure :) |
Change https://golang.org/cl/334269 mentions this issue: |
@neelance I made change for fixing this issue. Would you take a look? |
@neelance How can we proceed the review? If I need to do something, please let me know. I'll do it. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
arch-wasm
WebAssembly issues
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I'm running Wasm file with browsers which was compiled from Go source in my project. It works fine, but when I read
misc/exec_wasm.js
, I noticed that it did not enable strict mode. Enabling strict mode means:What did you expect to see?
The MDN document says:
Due to historical reasons, browsers don't enable strict mode by default, but it should be enabled to avoid several JS pitfalls. For example, TypeScript recommends enabling strict mode.
If this change looks good to maintainers, I could submit a patch for this following the strict mode migration guide.
What did you see instead?
misc/exec_wasm.js
did not enable strict mode.The text was updated successfully, but these errors were encountered: