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

Explore easing interop instance limitations #153

Open
elringus opened this issue May 15, 2024 · 0 comments
Open

Explore easing interop instance limitations #153

elringus opened this issue May 15, 2024 · 0 comments
Labels
enhancement New feature or enhancement

Comments

@elringus
Copy link
Owner

elringus commented May 15, 2024

  1. Consider marshaling only types with value semantics (structs, records and strings) and read-only collection interfaces (IReadOnlyCollection, IReadOnlyList). Other types (both concrete classes and interfaces) would be subject to instance bindings. Common collection types (array, list, dictionary) and their (mutable) interfaces (ICollection, IList, IDictionary) would have instance bindings as well, but with pre-built implementations on both sides (for example, to proxy APIs of JS array to C#'s List<> and vice-versa). Currently, only interfaces outside of system namespace are subject for instance bindings.
  2. Allow interop instances inside other interop instances. Currently, only top-level args (inside static export/import methods) are subject for instance bindings.
@elringus elringus added the enhancement New feature or enhancement label May 15, 2024
@elringus elringus added this to the First stable release milestone May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or enhancement
Projects
None yet
Development

No branches or pull requests

1 participant