-
Notifications
You must be signed in to change notification settings - Fork 18k
go to WebAssembly #18684
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
Comments
cc @griesemer |
I will be good/nice when this come from https://github.com/golang and not from the community-vendor-package ! |
There is ongoing llvm-go work happening now. We'll probably get wasm out of that. We can track this separately later. The llvm work is happening regardless of whether this wishlist bug is open. |
@bradfitz do you have any release(alpha, beta, rc, etc) date? nice :)
|
No, sorry. |
On Tue, Jan 17, 2017 at 11:35 AM, Brad Fitzpatrick ***@***.*** > wrote:
There is ongoing llvm-go work happening now. We'll probably get wasm out
of that.
Any details regarding whether is based on the gc or gofrontend?
From the current activity on the gofrontend repository, it looks like
llvm-go will be using gofrontend, not gc?
|
gofrontend |
I created a new WebAssembly tracking bug at #18892 for people to watch. |
Is there any plan for a go tool that transform go to webassembly? There is nothing/useful out there !
Look at this: https://www.reddit.com/r/golang/comments/5ai8ct/webassembly_browser_preview/ ... and
the last (thread) sentence of the bottomsome of the tread sounds not good (see below)The text was updated successfully, but these errors were encountered: