-
Notifications
You must be signed in to change notification settings - Fork 5
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
Pull Requests #1
Comments
Thanks a lot for the contribution! Let me go through your fork and see if there are breaking changes for us. |
Our functional tests pass. But the unittests seem to be failing for me:
Could you take a look? Thanks again for contributing! |
Indeed, the problem is On Wed, May 11, 2016 at 3:27 PM Max Grigorev [email protected]
|
Ah, ya been testing on 1.5. I was hoping to avoid doing a map lookup for the function pointer and wrapper data after we call back into Go (for performance reasons). We're already losing ~160ns every time we traverse between Go and C :-/. I'll try and get a rework committed in the next day or so. Thanks for the review! |
Looks too high, how did you measure that? Should not be more than a 100 or so instructions.
Thanks for doing the work! :-D |
That figure comes from Russ Cox (https://groups.google.com/d/msg/golang-nuts/NNaluSgkLSU/0bq1kXZueCwJ) and Mikael Gustavsson. It's mostly a result of go establishing a global local every time it crosses the go->c boundary |
Hey, just wondering if you guys are looking for/accepting pull requests into the project?
I've done some work on a fork (static casting between v8.Value and native go types and back, wrapped go objects with prototype handlers for functions and property handling). The changes add quite a bit of boilerplate to the code, but should provide more performance around marshaling data back and forth.
Code is available here: https://github.com/cchamplin/go-v8/commits/stage
Not sure if you're interested in that kind of thing but let me know.
The text was updated successfully, but these errors were encountered: