-
Notifications
You must be signed in to change notification settings - Fork 20
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
Re-implement duktape version using rust as glue code. #10
Comments
Omg yes! - This gets me mad excited |
Will this work occur on a branch? |
I see that there is already rust code in master. |
So I think these are the next steps. If anyone knows of a better plan of attack, let's talk about it.
Step 3 is large and will obsolete half the code written in 1 and 2, so should we just jump straight to it? |
@creationix Sounds like we should do number 3 first. |
I've been doing some research. There are existing duktape and libuv bindings for rust already on crates.io, but they are not complete or updated recently. I guess the next step is to write (or update/finish) rust bindings for the two languages. And start this as part of step 3 using our app as a way to manually test the integration. |
sounds like a good plan! a smaller first step is to get set up with cargo so that we're using rust via crates. thinking i might tackle that- thoughts? |
I'll start a new implementation that's started as a rust bin. We can leave the mostly C folder alone for now. |
I just added the rusty-duktape version. The main is just the sample from the getopts docs. A first step would be fixing that to use the nucleus CLI interface. |
https://twitter.com/creationix/status/740367352533909504
The text was updated successfully, but these errors were encountered: