Robin Kuzmin
Robin Kuzmin
Repo: https://github.com/microsoft/Quantum Dir: https://github.com/microsoft/Quantum/tree/main/samples Demo: http://aka.ms/try-qsharp Consider: * Sudoku solving with Grover's * Integer factorization (Shor's algo) - https://github.com/microsoft/Quantum/pull/619 * The samples that tell about simulation. We can add one...
[This article](https://docs.microsoft.com/en-us/azure/quantum/user-guide/testing-debugging?tabs=tabid-vs2019) makes me think that at least one simulator has to be specified for a unit test (even if the simulator is not used). If we make the simulator...
(Request For Early Feedback. Work in Progress) **Latest State** * [Brief Illustration of the Proposed Changes](https://github.com/microsoft/QuantumLibraries/issues/419#issuecomment-791734972) (with Code Fragments and Usage Examples) * [What Happens to DoubleAsStringWithFormat() and IntAsStringWithFormat()](https://github.com/microsoft/QuantumLibraries/issues/419#issuecomment-790258665). *...
After the [SparseSimulator is added](https://github.com/microsoft/qsharp-runtime/pull/918), consider adding to the `QuantumLibraries` the support for the SparseSimulator. In particular * In [Standard/src/Diagnostics/Emulation/Internal.cs](https://github.com/microsoft/QuantumLibraries/blob/main/Standard/src/Diagnostics/Emulation/Internal.cs) consider replacing all the occurrences of `QuantumSimulator` with [`CommonNativeSimulator`](https://github.com/microsoft/qsharp-runtime/tree/main/src/Simulation/Simulators/CommonNativeSimulator) -...
[This line](https://github.com/microsoft/qsharp-runtime/blob/352aba026cb5f81a5b0f2ad720aee5c969547551/src/Qir/Runtime/lib/QIR/arrays.cpp#L124) does not guarantee the proper alignment of the buffer pointed to by the `QirArray::buffer`. The C++ standard allows the allocation to be 1-byte aligned, 2-byte aligned, etc., which...
Works around the issue with linker warnings. Item 42842.
Related: https://github.com/microsoft/qsharp-runtime/issues/975 https://github.com/microsoft/QuantumLibraries/issues/546 Consider moving [this assert](https://github.com/microsoft/qsharp-runtime/blob/499c068d3addc187b8cba30f718ba68f7d4b0e84/src/Qir/Runtime/lib/QIR/callables.cpp#L259) to [here](https://github.com/microsoft/qsharp-runtime/blob/499c068d3addc187b8cba30f718ba68f7d4b0e84/src/Qir/Runtime/lib/QIR/callables.cpp#L407), [here](https://github.com/microsoft/qsharp-runtime/blob/499c068d3addc187b8cba30f718ba68f7d4b0e84/src/Qir/Runtime/lib/QIR/callables.cpp#L440), and [here](https://github.com/microsoft/qsharp-runtime/blob/499c068d3addc187b8cba30f718ba68f7d4b0e84/src/Qir/Runtime/lib/QIR/callables.cpp#L449). Such that the null callables are created and exist successfully until the moment of invocation.
(Windows) The Spectre-mitigated libs of VS2022 cause linker warnings (see below) when [building QIR runtime](https://github.com/microsoft/qsharp-runtime/blob/77edcf31dc0da53ecd568455f4310000b2332c97/src/Qir/Runtime/CMakeLists.txt#L19-L32), but don't cause such warnings when[ building the native part](https://github.com/microsoft/qsharp-runtime/blob/77edcf31dc0da53ecd568455f4310000b2332c97/src/Simulation/Native/CMakeLists.txt#L40-L56) of the full-state simulator. See...
**2022.05.02** Actually we do sanitize the native part of the QuantumSimulator. [Here](https://github.com/microsoft/qsharp-runtime/blob/498b6e7ba04ad99a27d9aa1d5385529ed92629e0/src/Simulation/Native/build-native-simulator.ps1#L25-L42), [here](https://github.com/microsoft/qsharp-runtime/blob/498b6e7ba04ad99a27d9aa1d5385529ed92629e0/src/Simulation/Native/build-native-simulator.ps1#L66), and [here](https://github.com/microsoft/qsharp-runtime/blob/498b6e7ba04ad99a27d9aa1d5385529ed92629e0/src/Simulation/Native/build-native-simulator.ps1#L75). That is built and executed in the Debug config only by the `microsoft.qsharp-runtime.sanitized` pipeline (see...