|
Ran
|
Jobs
1
|
Files
987
|
Run time
5min
|
Badge
README BADGES
|
push
github
Make `qargs` const in two `QkTarget` functions (#17048) * Make `qargs` const in two `QkTarget` functions `qk_target_entry_add_property` and `qk_target_update_property` declared `qargs` as `*mut u32`, so the generated header exposed it as `uint32_t *`. Neither function writes through the pointer; both pass it straight to `parse_qargs`, which already takes `*const u32`. Callers from languages that track const-ness more strictly than C had to cast it away for no reason. The rest of the C API already treats qubit-index inputs as const, including `qk_target_instruction_supported` and `qk_target_op_qargs_index` in this same file, so this brings the two outliers into line. Existing C code is unaffected: relaxing a parameter to `const` only widens what callers may pass. Assisted-by: Claude Opus 5 * Remove release note * Revert "Remove release note" This reverts commit d3d98858c. * Upgrade release note
2 of 2 new or added lines in 1 file covered. (100.0%)
1 existing line in 1 file now uncovered.123199 of 139733 relevant lines covered (88.17%)
936737.62 hits per line
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 1 |
90.32
|
0.0% | crates/circuit/src/parameter/parameter_expression.rs |
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 37014974799.1 | 987 |
88.17
|
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|