Mike Anderson

I think we can safely assume the existence of matrices and vectors as return types. I think it is more about the specification of the inputs / outputs. For vectors...

Yeah.... keyword arguments make things complex for implementers, they need to be very precise in how behaviour works for all combinations of parameters. We've already seen variance between implementations. Guess...

@astanin I like your proposals, certainly helpful to have more readable keywords here Happy to take patches that improve things here, though it may cause some downstream breakage. I think...

@kasterma: good suggestion, though I think that is worth a separate issue. I'll create one.

https://github.com/mikera/matrix-api/issues/40

Well we probably ultimately want two versions (immutable and mutable) of each: `set-row` and `set-row!` for example. The mutable versions could certainly be implemented with an mutable view. The immutable...

We'll get mutable + immutable versions of most operations for free if we complete the Incanter / core.matrix integration. Most core.matrix functions already have immutable and mutable versions where it...

slicing schemes as first class objects is an interesting idea, I'd be interested to see an implementation that demonstrates that it can be done efficiently and in a general way....

Row setting implemented in this commit: https://github.com/mikera/core.matrix/commit/95993eaf9c4b77a866e538cd2784d8e4f13dadeb Still not sure of how to handle the more general strategy....

Part of the reason of `e` is to avoid collisions with `clojure.core`. The reason some things are in the `operators` namespace is that these are things that you may want...