Mariia Mykhailova

I would suggest creating a new folder under https://github.com/microsoft/qsharp/blob/main/samples/ called "python_interop", and add two projects to it, each in its own folder: 1. [Teleportation project from our documentation](https://learn.microsoft.com/en-us/azure/quantum/user-guide/how-to-work-with-qsharp-projects?tabs=tabid-qsharp%2Ctabid-python-run#steps-for-creating-a-q-project), covering the...

I skimmed through our algorithms samples, the next most confusing one is Teleportation: it says teleporting one-qubit state but DumpMachine has two qubits. We should be able to use DumpRegister...

Can we do qubit_release upon any error, as part of error processing?

I'm not bothered by the time it takes to validate the katas in CI builds (this will only grow as we move from 10 katas to 40), but when I...

Still open

I have two possible suggestions for this API: * Add M.Q.Convert.DoubleAsStringWithPrecision that would allow only to format a number with a specific number of decimal digits - that's enough for...

There absolutely is value in converting data types into strings! In another project (I haven't updated that to Modern QDK yet) I'm using string representation of a callable (its name)...

Any updates on converting callables into strings? I ended up using a workaround for Complex and CompexPolar types in the ComplexArithmetic kata, though I still want to convert UDTs into...

In my scenarios I need callables that are defined globally, I don't really expect a reasonable name printed for a lambda. In Classic QDK, an internal name was printed: ```qsharp...

For VS Code, I'm happy to for it to be a message, like DumpMachine output is. But it we want to make it available on the website, plain text would...