infinyon / infinyon/node-bindgen
Tracking: Custom future execution engine that integrates with Node's thread execution engine
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 587
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Nodebindgen uses async-std/smol to execute future task. However, Nodejs has it's own execution infrastructure result in duplicate thread pool. This issue investigate possible way to integrate them efficiently.
With latest changes in smol, it is probably possible to execute Rust's future task in Nodej's thread pool.
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
The issue names no files, tests, or entry points. Start by locating the async-std/smol execution path and the Node.js thread-pool integration points. Done means establishing whether Rust futures can use Node.js's thread pool efficiently without a duplicate pool.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, rust
- Domain
- backend, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100