Scott Carda
Scott Carda
Q# projects that make references to Q# executable projects cause an issue with C# generation, creating duplicate definitions for generated classes. This PR addresses this in the samples by changing...
Updates the naming scheme used for generated callables and local variables in the Q# compiler. Generated callables names will all have a GUID surrounded by double underscores prepended to the...
The logic for determining if we should generate QIR for a particular target should live in the SubmitterFactory as a static function, `TargetSupportsQir`. That function should then be called in...
**Please describe what you would like the feature to accomplish.** When the `` is not provided in a Q# project, the system sets a default path for this to be...
In AzureClient.cs, we define and use function `IsQuantumExecutionTarget` to determine if a target is quantum-executable. Instead we should use the API provided by the Service defined here: https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/quantum/Microsoft.Azure.Management.Quantum/src/Generated/QuantumManagementClient.cs#L82
The output for the full state simulator should be formatted in the same way as running the job on a local simulator. Specifically, all messages encountered during the program should...
It was suggested in this [ToDo in QirMagic.cs](https://github.com/microsoft/iqsharp/blob/sccarda/implement-qsharp-submitter/src/Kernel/Magic/QirMagic.cs#L51) that the entry point generator should be moved out of the Azure Client project.
All other Azure targets have a `.mock` target associated with them, such as `honeywell.mock`. There is not a corresponding `.mock` target for the `microsoft.simulator` target. Creating one would allow us...
1. Adds the `LoadFrom` public function to allow the Runtime to load a `BitcodeModule` from qir bitcode. 2. Fixes issue where OutputRecording definitions' parameter construction had mixed up the case...