Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Change casting rules for StateMP to avoid copy in Lightning (#5995)
### Before submitting Please complete the following checklist when submitting a PR: - [x] All new features must include a unit test. If you've fixed a bug or added code that should be tested, add a test to the test directory! - [x] All new functions and code must be clearly commented and documented. If you do make documentation changes, make sure that the docs build and render correctly by running `make docs`. - [x] Ensure that the test suite passes, by running `make test`. - [x] Add a new entry to the `doc/releases/changelog-dev.md` file, summarizing the change, and including a link back to the PR. - [x] The PennyLane source code conforms to [PEP8 standards](https://www.python.org/dev/peps/pep-0008/). We check all of our code against [Pylint](https://www.pylint.org/). To lint modified files, simply `pip install pylint`, and then run `pylint pennylane/path/to/file.py`. When all the above are checked, delete everything above the dashed line and fill in the pull request template. ------------------------------------------------------------------------------------------------------------ **Context:** The changes made in #5547 led to a performance regression in Lightning because a superfluous state vector copy is made when adding `0.j`, which was introduced to cast the output to complex. **Description of the Change:** Use `qml.math.cast` instead. **Benefits:** Avoid unnecessary sum of `0.j` **Possible Drawbacks:** **Related GitHub Issues:** [sc-65127]
- Loading branch information