You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hope all are well. So, I have been thinking about this for quite a while, and would like to know what you (the users) think. At the moment, quick mix and matches use of primitives and numpy arrays based on convenience, which whilst making life a bit easier does create inconsistencies with respect to parameter types and returns for data such as statevectors and operators.
Goal of this discussion is to speculate whether quick should solely use primitives with flexible support of numpy arrays, or the current state is optimal.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Greetings there,
Hope all are well. So, I have been thinking about this for quite a while, and would like to know what you (the users) think. At the moment,
quickmix and matches use of primitives and numpy arrays based on convenience, which whilst making life a bit easier does create inconsistencies with respect to parameter types and returns for data such as statevectors and operators.Goal of this discussion is to speculate whether
quickshould solely use primitives with flexible support of numpy arrays, or the current state is optimal.Beta Was this translation helpful? Give feedback.
All reactions