Angela Burton

Hi @Manvi-Agrawal! I wanted to check in on what your plans are for this PR and if you still planned to add the changes in this or next month. I'll...

Hi, @Manvi-Agrawal! I wanted to check in to see if you still planned to push these changes. If not, we can make the final round of edits to get everything...

Hi @Manvi-Agrawal! Your design document looks good to me. For 3a, determining the simulators specified, [this](https://github.com/microsoft/iqsharp/blob/252088342ff3dd6bc7be374ded2b0c0e750a003d/src/Kernel/Extensions.cs#L101) iqsharp code should be useful reference. In that line we're retrieving details about documentation,...

Thank you for reporting this! It should be fixed now with #685, but please feel free to reopen if you're still experiencing this bug.

Hi! Currently %simulate doesn't support passing an operation as an argument. A workaround would be to define an operation `operationAWithB` that passes `operationB` to `operationA`, then call that through `%simulate...

To add Range as a parameter option for magics that run locally (i.e. `%simulate`, `%debug`, etc), a converter will need to be added to [TupleConversion](https://github.com/microsoft/iqsharp/blob/main/src/Core/TupleConversion.cs) for the type `QRange`. These...

Changes should be made to [ResultConverter](https://github.com/microsoft/iqsharp/blob/4324d1d6de03102edf5fd210b6f22655ee9b6fa2/src/Core/TupleConversion.cs#L195) to update this behavior.

Thank you for the feedback! After consideration we've decided to stick with the current design on this, with the workarounds as noted in the above thread.

This looks like an issue that arises when parameters are deserialized in `OperationInfo.GetRunArguments`. Adding a custom converter to [JsonConverters.TupleConverters](https://github.com/microsoft/iqsharp/blob/d75f203ef70910b92500b861f34fd3fdad1f0944/src/Core/TupleConversion.cs#L31) would allow for the correct error handling. The default deserialization could...