Mathias Soeken

I suppose that `RippleCarryAdderD` could be updated. However, it's not just replacing existing `CCNOT` since the current implementation used two `CCNOT` for each `Carry`, where only one is necessary. It...

@QuXing9: I am transferring this issue, since `AssertQubitWithinTolerance` is implemented in this repository. It seems that the problem arises from this line: https://github.com/microsoft/qsharp-runtime/blob/e5be79bf9781f228c99b5d0d1d7ccd944ef20a89/src/Simulation/Simulators/CommonNativeSimulator/AssertProb.cs#L46 where a `>` comparison is used, which...

I would call the operation `ApplyTableLookup` or `ApplyXorFromAddress`. If we choose the latter, the name table lookup should appear in the docs for discoverability. The `data` is not padded with...

@vivekmthr Just checking back with you, whether you found some time to look into one of the READMEs? I am happy to help, if I can.

Thanks @vivekmthr

@unnati914 Sure, you can work on this issue. I suggest to just open a PR and mention this issue in there. The PR does not need to address all READMEs...

@buseorak Thanks for offering to work on this issue. The 6 READMEs are just an example, but a good way to start. As mentioned above, simply open a PR and...

This seems to be related to Q# interoperability with Python. I am transferring this issue to microsoft/iqsharp.

Thanks for the proposal, @cgranade. Here are some comments: * The return type seems broken in `Reshaped2To3` and `Reshaped3To3` * Will there be a function called `Size` for consistency with...

@cgranade I agree to include `BigInt`-variants for all `Int` methods as part of the changes with #337. In general, I think that having Q# bit-int-by-default as mentioned by @Strilanc is...