rigetti / rigetti/qcs-sdk-rust
Errors are not particularly helpful
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Rust
- Stars
- 15
- Forks
- 4
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 1
Description
For example, when calling compile with a TargetDevice that fails to deserialize, one receives the error
qcs.CompilationError: invalid type: null, expected f64 at line 1 column 159
This could be improved by saying what part of compilation failed (deserializing the TargetDevice).
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 at the compile entry point and follow the TargetDevice deserialization path that produces CompilationError. Reproduce the invalid-type example and update the reported error so it identifies that deserializing the TargetDevice failed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100