I think the main problem is that is just hasn't been sufficiently developed and tested.
core.matrix.complex was an experiment to show that:
a) complex numbers can be used with the core.matrix API - it was a design goal of core.matrix that arbitrary element types should be supported, and it was nice to confirm this
b) You can create complex matrices using, for example, two regular real matrices as the underlying storage and define efficient operations using these. This is interesting as it opens the possibility for stuff like e.g. GPU two accelerated arrays to "automatically" be treated as complex arrays.
In order to develop this to the point that this is generally useful, someone would need to:
1) complete the implementation (e.g. implement some protocol for things like inner-product to make mmul work)
2) probably add some tests for things that are complex-specific.
There would also need to be some thought about what some of the API functions actually mean given complex arrays. Stuff like adding is obvious, but for some of the matrix decompositions etc. things could get complex (pun intended). This could however be deferred and supported later.
Vic, if you want to have a crack at any of this then I'd be delighted and happy to advise and answer questions, but haven't got much time to work directly on this right now (as I don't need complex numbers in my current work).