Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update Playground WebAssembly to Go 1.11 #33

Closed
DeedleFake opened this issue Oct 19, 2017 · 4 comments
Closed

Update Playground WebAssembly to Go 1.11 #33

DeedleFake opened this issue Oct 19, 2017 · 4 comments
Assignees
@DeedleFake
Labels
playground

Comments

@DeedleFake
Copy link
Owner

DeedleFake commented Oct 19, 2017 •
edited

Waiting on gopherjs/gopherjs#705.
@DeedleFake DeedleFake self-assigned this Oct 19, 2017
DeedleFake added a commit that referenced this issue Oct 19, 2017
@DeedleFake
Update WDTE. Use the standard importer and note disabled modules.
ea56e89 
Part of #33.
@DeedleFake DeedleFake changed the title The Playground Needs Updating Implement io Module for Playground Mar 15, 2018
@DeedleFake DeedleFake mentioned this issue Mar 22, 2018
Open
@DeedleFake DeedleFake changed the title Implement io Module for Playground Use WebAssembly for the Playground instead of GopherJS Jul 20, 2018
@DeedleFake
Copy link
Owner Author

GopherJS is nice, but WebAssembly should be much nicer. As of Go 1.11beta1, Go now has native, if a tad limited, support for WebAssembly. Switching from GopherJS should provide a workaround for gopherjs/gopherjs#705 as well as, hopefully, fix the context-cancellation problem that the playground currently has.

@DeedleFake
Copy link
Owner Author

DeedleFake commented Aug 13, 2018 •
edited

Initial testing using Go 1.11beta3 finds that this does, in fact, fix the import 'io' issue, but it does not seem to fix the context-cancellation problem. There also doesn't appear to be a clean way to expose Go functions to the JavaScript side at the moment, and all Go WASM modules need to be wrapped in a 400+ line JavaScript wrapper hidden inside $GOROOT/misc/wasm. It's definitely feasible, though, and probably worth it just to fix the import 'io' issue and finally allow Playground code to be completely compatible with the standard library.

Edit: Not quite compatible. Forgot about io/file. Maybe that'll make sense at some point, too, though... Hmmm...

@DeedleFake
Copy link
Owner Author

The Playground is now moved over to WebAssembly, but I'm leaving this open until Go 1.11 comes out, as the WebAssembly support could wind up being a bit different than it is currently.

@DeedleFake DeedleFake changed the title Use WebAssembly for the Playground instead of GopherJS Update Playground WebAssembly to Go 1.11 Aug 13, 2018
@DeedleFake
Copy link
Owner Author

It wasn't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DeedleFake DeedleFake

Labels
playground
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DeedleFake