-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Use np.complexfloating for dtypes that should be complex #5488
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mpharrigan
approved these changes
Jun 22, 2022
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.
cool. much better type info
@@ -170,7 +171,7 @@ def get_result(state: np.ndarray, sample: float): | |||
qubits=cirq.LineQubit.range(4), | |||
prng=mock_prng, | |||
initial_state=np.copy(state), | |||
dtype=state.dtype, | |||
dtype=cast(Type[np.complexfloating], state.dtype), |
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.
can change this cast
to an assert
earlier?
rht
pushed a commit
to rht/Cirq
that referenced
this pull request
May 1, 2023
…5488) This changes the type signature for dtypes that should only be `np.complex64` or `np.complex128`. There are also dtypes in `qis.states.py` but I've not changed these over, as they are often called the `dtype` of a `np.array`, and so they will often need to be cast. This fixes some `check/mypy --next` errors. Technically a breaking change in type signature (more restrictive), but we yell when types are not complex.
harry-phasecraft
pushed a commit
to PhaseCraft/Cirq
that referenced
this pull request
Oct 31, 2024
…5488) This changes the type signature for dtypes that should only be `np.complex64` or `np.complex128`. There are also dtypes in `qis.states.py` but I've not changed these over, as they are often called the `dtype` of a `np.array`, and so they will often need to be cast. This fixes some `check/mypy --next` errors. Technically a breaking change in type signature (more restrictive), but we yell when types are not complex.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
BREAKING CHANGE
For pull requests that are important to mention in release notes.
kind/health
For CI/testing/release process/refactoring/technical debt items
size: M
50< lines changed <250
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes the type signature for dtypes that should only be
np.complex64
ornp.complex128
.There are also dtypes in
qis.states.py
but I've not changed these over, as they are often called thedtype
of anp.array
, and so they will often need to be cast.This fixes some
check/mypy --next
errors.Technically a breaking change in type signature (more restrictive), but we yell when types are not complex.