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.

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

[WIP] ffi support #9173

Closed
wants to merge 1 commit into from
Closed

[WIP] ffi support #9173

wants to merge 1 commit into from

Conversation

manyuanrong
Copy link
Contributor

FFI support based on libffi.

Related issues and PRs:

#8490
#7564

@manyuanrong manyuanrong force-pushed the ffi branch 2 times, most recently from 63909a0 to 8732971 Compare January 21, 2021 04:11
@lin7sh
Copy link

lin7sh commented Jan 22, 2021

I think the big effort of Wasm and Wasi is keeping js away from ISA dependent binary code, why bring FFI back to make it complex again? I think someone could argue that they need FFI for low level hardware access, but it think it could provide by the runtime(browser or deno) itself for standardisation. Have a look of the new Web Serial API and Web NFC API in Chrome 89. A restricted but "run everywhere" is unique and is its strength for deno comparing to go and rust.

Base automatically changed from master to main February 19, 2021 14:59
@bartlomieju
Copy link
Member

Thank you for the PR @manyuanrong, we've been discussing FFI internally from time to time and will probably look into shipping it at some point. I'm gonna close this PR as it is stale and there's been a lot of changes to the ops interface since it was open, but we'll definitely circle back to it as a reference point if we decide to implement FFI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants