Graph API
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.4k
- Forks
- 249
- PR merge metrics
- No merged PRs in 30d
Description
First, thanks for all of the excellent work on this! I have a workload which could benefit from the Graph API (as opposed to just using individual stream submissions and such).
Any ideas on LOE to implement, what current blockers are, and so on?
Perhaps we can discuss what getting started on implementing this should look like, desired API style, and all that.
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 does not name any files, tests, or entry points. Start by locating the existing stream-submission API and any current graph or CUDA execution abstractions, then review the discussion needed to define the API style and blockers. Done means an agreed Graph API design and an implementation plan with clear scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100