Several katas could have better error messaging:

• Superposition : the test harness could log the actual state of the system after prep vs the expected state before asserting that they are the same (the change would add state prep and logging using DumpMachine to AssertEqualOnZeroState)
• BasicGates : a similar improvement, but a bit more extra code to write a unified test wrapper

Here are some examples:

• Root README is missing machine learning category of samples
• README in algorithms is missing repeat-until-success and sudoku-grover
• [README in diagnostics](https://github.com/microsoft/Quantum/blob/main/samples/diagnostics/RE

Most documentation comments in the compiler only use the <summary> tag. For short comments, this is fine, but in many cases the summary is several paragraphs long and would be easier to read if it used standard documentation tags to structure the information. This is especially important for exceptions - exceptions mentioned in the <summary> tag are easy to miss, whereas the special `<exceptio

Describe the bug
If I provide Partitioned an array of length N and partition sizes of total length N, the return contains an extra partition of length 0 in the end. This makes it inconvenient to use: if I want to split an array into K parts of equal length ([example](https://github.com/microsoft/Quantum

When the Q# entry point has a parameter with no associated documentation, the description of the option on the command line is blank:

@EntryPoint()
operation Foo(myParam : Int) : Unit {}

> dotnet run
Option '--my-param' is required.

Usage:
  App [options] [command]

Options:
  --my-param <my-param> (REQUIRED)
  -s, --simulator <simulator>         The name of th

Looking for a Zookeeper who can help manage and drive more algorithms to be implemented in the zoo!

https://github.com/qsharp-community/algorithm-zoo