Guen Prawiroatmodjo
Guen Prawiroatmodjo
@cgranade, the binder-index.md page says "Quantum Development Kit samples" and specifically mentions Q#, so I am not sure if this sample fits into the current index. I would add another...
This PR contains changes from https://github.com/microsoft/Quantum/pull/675 as well
After some thought it looks like this won't be a straightforward fix so we are going to include this in https://github.com/microsoft/QuantumLibraries/issues/337, so will close this for now. Thanks @crazy4pi314 for...
Reopening this issue and assigning our new `Status-ChildIssue` label so we can track it as part of the #337 proposal.
It looks like the issue was resolved when installing Python 3.7.3. I'm wondering if this is a regression. Our [docs ](https://docs.microsoft.com/en-us/azure/quantum/install-python-qdk?tabs=tabid-dotnetcli) mention that the QDK is compatible with Python>3.6.
@cgranade it seems like having a simulator with noise would be a feature request here as well?
+1 to fixing this, I ran into this today and it was very confusing.
@rmshaffer it seems that this is not the intended usage of the library functions, instead, the recommended route is to create a Q# application and import the operation there. I...
@rmshaffer Oh great! How is this functionality currently used? And how does this work if the operation contains "unsafe" variables (such as qubit registers), does it pass the error from...
@rmshaffer Yes I think that approach would work well! Does the wrapper code currently consist of one or multiple files? I would think that aside from the entrypoint program we...