Chris Cook

Yeah, let's consider it for v2.0.0 since it will change (and potentially break) how people might use v1.

Yes, I agree with your point. I will remove it.

Hmm interesting! Does it work in 5?

If it works in all odd dimensions it makes it still useful and out of the scope of p5's cross function.

Interesting... If it gives a complex result in other dimensions it might still be useful. In which case we should probably also think about introducing complex numbers.

Thanks for bringing this up. I did look at this when implementing it, the issue is that we want to provide a consistent API so splitting the method into two...

I think a suitable way of checking for a matrix would be something like this: ```js function isMatrix(obj) { if ( !obj.size || obj.size.length !== 2 || !obj.data ) {...

To answer your question, no, there's no real reason. They are attached to the p5 prototype, so you can create them with `p5.nVector` etc, you might be able to use...

Sorry I didn't manage to take a look at this yet, I'm not quite sure why it's not pointing to the correct place anymore as it still seems to be...

@max0410 are you familiar with TypeScript and able to work with it? If so I might work on re-organizing the code as TS files then bring them together compile-time.