rigetti / rigetti/qcs-sdk-rust
Consider how falling back to the default client should be handled
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15
- Forks
- 4
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 1
Description
Qcs::load() is currently infallible. It will attempt load a QCS config from disk and fallback to a default one if it fails to do so. Per this comment, we should consider making the fallback behavior opt-in via an alternate method.
Contributor guide
No contributing guide indexed for this repository
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 reading Qcs::load() and the linked pull request review comment to understand the current disk-loading and default-client fallback behavior. Done means reaching a clear decision about whether fallback should be opt-in through an alternate method and documenting the expected API behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100