Consider refactoring client/server pass pipeline to use common code
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 456
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Description
In the future, we may want to look at how to combine this (client/server pass pipeline splits in RemoteRestRuntimeClient) with addPipelineToQIR so that we use common code for all these places that do passes lest the pass pipeline differences become unmaintainable.
Originally posted by @bmhowe23 in https://github.com/NVIDIA/cuda-quantum/pull/1012#discussion_r1449163223
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
Start by locating the client/server pass-pipeline split in RemoteRestRuntimeClient and the addPipelineToQIR entry point. Compare how each assembles and applies passes, then define the shared behavior that would replace both paths; done means the pipelines use common code without losing their client/server distinctions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100