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

Design and implement Dart VM FFI #34452

Open
mraleph opened this Issue Sep 12, 2018 · 3 comments

Comments

Projects
None yet
4 participants
@mraleph
Contributor

mraleph commented Sep 12, 2018

@lrhn

This comment has been minimized.

Show comment
Hide comment
@lrhn

lrhn Sep 14, 2018

Member

A general FFI could also be useful for interaction with JavaScript, so we should consider whether it's possible to make something general wihout compromising on the usability on each platform.

The current JS-interop functionality is not a clean design, it should be possible to improve it.

Member

lrhn commented Sep 14, 2018

A general FFI could also be useful for interaction with JavaScript, so we should consider whether it's possible to make something general wihout compromising on the usability on each platform.

The current JS-interop functionality is not a clean design, it should be possible to improve it.

@matanlurey

This comment has been minimized.

Show comment
Hide comment
@matanlurey

matanlurey Sep 14, 2018

Contributor

@lrhn:

The current JS-interop functionality is not a clean design, it should be possible to improve it.

I would not assume that without talking to @vsmenon. The syntax might leave a little to be desired, but I have no desire to make a breaking change to the syntax unless it vastly improves end users, not just the fact it isn't a "clean design".

Contributor

matanlurey commented Sep 14, 2018

@lrhn:

The current JS-interop functionality is not a clean design, it should be possible to improve it.

I would not assume that without talking to @vsmenon. The syntax might leave a little to be desired, but I have no desire to make a breaking change to the syntax unless it vastly improves end users, not just the fact it isn't a "clean design".

@vsmenon

This comment has been minimized.

Show comment
Hide comment
@vsmenon

vsmenon Sep 14, 2018

Member

Providing a new syntax / library doesn't necessarily imply removing the existing support. With that in mind, I think @lrhn 's suggestion is good.

Member

vsmenon commented Sep 14, 2018

Providing a new syntax / library doesn't necessarily imply removing the existing support. With that in mind, I think @lrhn 's suggestion is good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment