acroy

@jrevels : Maybe not. Lexicon and Docile manuals have sections "Manual" and "API", which would do for external and internal documentation. We just have to figure out how it works...

You are right, we shouldn't use the "API" section for internal documentation. The latter is really for us to keep track of implementation details etc. But in any case it...

Like you both said, the different pictures only make sense if you have information about the time evolution. A quantum object given by a `QuArray` doesn't know about this. My...

Using a Type parameter seems to be a better solution. But in any case we need to have a propagator type before we can work out the details. Note that...

Definitely required. There are, however, more functions like `complex`. So the question is if/how we can support all of them in an elegant way?

The "easy" way would be to use code generation to provide functions for `float`, `float16`, `float32`, etc. But I have the feeling that this is not the best (and future...

Thanks @jrevels. Good to know that it is fixed in 0.4. I don't know the schedule for releasing 0.4 since I didn't (couldn't) follow the developments over summer. Since it...

I think right now this is not easily possible. Note that `QuArray`s are really meant to be containers for the coefficients. The information about the basis would be stored in...

Partial trace (and transpose) is certainly on our wish list (see also issue #7). As Amit said there is an implementation in QuDOS, but I didn't want to port it...

Yeah, I am not sure about `QuStateVec`, but I think some sort of density matrix type is useful/necessary. Firstly, note that your `QuOuter` only covers pure states. A general (mixed)...