-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Follow-up for native support for Sparse Hamiltonians expval() #296
Conversation
…ane-lightning into feature/Kokkos-sparse
…ane-lightning into feature/Kokkos-sparse
…g-tidy inspection
…ane-lightning into feature/Kokkos-sparse
Codecov Report
@@ Coverage Diff @@
## master #296 +/- ##
=======================================
Coverage 99.44% 99.44%
=======================================
Files 30 30
Lines 3410 3410
=======================================
Hits 3391 3391
Misses 19 19
Continue to review full report at Codecov.
|
…ane-lightning into feature/Kokkos-sparse
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @AmintorDusko. Just a minor suggestion; no blocking and happy to approve anyway.
Co-authored-by: Ali Asadi <[email protected]>
Hi @AmintorDusko. Great job on both PRs 🚀 I also have some general suggestions for your other PR #283 (will be added shortly). Could you please apply those in this PR before merging? |
Before submitting
Please complete the following checklist when submitting a PR:
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
tests
directory!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
.Ensure that the test suite passes, by running
make test
.Add a new entry to the
.github/CHANGELOG.md
file, summarizing thechange, and including a link back to the PR.
Ensure that code is properly formatted by running
make format
.When all the above are checked, delete everything above the dashed
line and fill in the pull request template.
Context:
Small follow-up PR for fixing problems with wheels.
Description of the Change:
Benefits:
Properly render Readme on PyPI
Possible Drawbacks:
Related GitHub Issues: