Skip to content

docs: correct the consequence of repetition in loop operations

Qingzhen Wangrequested to merge
doc-correction-loop-operations into main

Explanation of changes

DOC-578 ticket.

  1. I have tested, see the MFE in the DOC ticket, that Y-gate in this case only occurs once. Thus want to correct the explanation in the page.
  2. I do not know exactly how to phrase the original statement "Repetition loops act on all port-clock combinations present in the circuit. " Therefore I just add a "NOT" in the sentence. But if someone is knowledge of this exact behavior then this can be written better.

Motivation of changes

Motivate why the particular solution was chosen.

Merge checklist

See also merge request guidelines

  • Merge request has been reviewed (in-depth by a knowledgeable contributor), and is approved by a project maintainer.
  • New code is covered by unit tests (or N/A).
  • New code is documented and docstrings use numpydoc format (or N/A).
  • New functionality: considered making private instead of extending public API (or N/A).
  • Public API changed: added @deprecated and entry in deprecated code suggestions (or N/A).
  • Newly added/adjusted documentation and docstrings render properly (or N/A).
  • Pipeline fix or dependency update: post in #software-for-developers channel to merge main back in or update local packages (or N/A).
  • Tested on hardware (or N/A).
  • CHANGELOG.md for breaking changes and AUTHORS.md have been updated (or N/A).
  • Update Hardware backends documentation if backend interface change or N/A
  • Check whether performance is significantly affected by looking at the Performance metrics results.
  • Windows tests in CI pipeline pass (manually triggered by maintainers before merging).
    • Maintainers do not hit Auto-merge, we need to actively check as manual tests do not block pipeline

For reference, the issues workflow is described in the contribution guidelines.

Merge request reports