-
Notifications
You must be signed in to change notification settings - Fork 699
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
Rename the project? #101
Comments
We may end up wanting to use it in some cases where we currently use binaryen if Binaryen's IR diverges from wasm proper. So currently it's a text/binary encoder/decoder, an interpreter, and... anything else? Sort of analogous to binutils, but I wouldn't necessarily want to call it something derived from 'binutils' exactly unless we want to provide all those tools. Does sexpr-wasm do much handling or dumping of the various non-code sections currently? Other tools might include dumping the names section if it exists (a la nm), and maybe even more arbitrary sectiony stuff like objcopy. If we don't want to be 'binutils' we could say wasm-utils or wasm-tools, but that's pretty generic. Even a wasm-binutils or wasm-binary-tools or some such doesn't quite capture it since it has an interpreter :) |
It can generate a JavaScript test file from a spec test. But yeah, not much else. sexpr-wasm is basically just a C implementation of ml-proto.
Yes, it can read or write the names section w/ a flag. Otherwise it strips it. I think it's reasonable to support other non-code sections too, when they come along.
I think some users do like that it is standalone and relatively simple. At least, I do. :)
I guess that's the nice thing about picking a non-descriptive name -- you can make it do whatever you want :P |
|
WASM binary toolkit? Then again, I'm a fan of cutesy names, so maybe On Fri, Sep 16, 2016 at 2:36 AM, Derek Schuff notifications@github.com
|
WebAssembly Toolkit (WAT?) |
I was thinking about it, and the main differentiating factor is that it is written in C. So maybe just That said, |
I'm voting all my TL points for Wabbit, however many that is :-D On Fri, Sep 16, 2016 at 8:06 PM, Ben Smith notifications@github.com wrote:
|
Derek and I have started calling it Wabbit. Let's go ahead and make that change :) |
Renamed the repo! Looks like the next steps are:
|
Looks like Travis CI is working again. |
This seems to be done. Who needs to be mailed? @s3ththompson can you do this? |
Oh, and can you change the project description too? It still says "sexpression -> wasm" :-) |
Updated description and sent out the name change to the other browsers as an FYI. |
sexpr-wasm-prototype is a very old name for the project, and doesn't really reflect what it is or does. Any ideas for a better name?
The text was updated successfully, but these errors were encountered: