microsoft / microsoft/node-api-dotnet
Does Memory<T> type work for dynamic JS->.NET invocation?
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 783
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
Based on my experiment, I found it doesn't work, this usage may need code generation. byte[] type works well in dynamic JS->.NET invocations.
It would be good if this can be confirmed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported dynamic JS-to-.NET invocation with Memory and compare it with the working byte[] case. Confirm whether Memory is unsupported and whether code generation is required, then document the result and any relevant entry point or test identified during the investigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100