If we introduced Covectors and a row slice of a Matrix was a Covector, then
this wouldn't be an issue anymore since we could simply allow sorting both
Vectors and Covectors but not Matrices. There's still the open question of
what taking a slice that looks like T[1,:,1] should produce. That's a
one
I hadn't seen that issue; thanks for the link. I'm glad there's a
discussion going on about that. :)
-- Leah
On Mon, Jul 21, 2014 at 10:43 AM, Ivar Nesje wrote:
> Warning for 2d row vectors used in context where only a 1d column vector
> is used could definelty be implemented as help when you
Warning for 2d row vectors used in context where only a 1d column vector is
used could definelty be implemented as help when you get a MethodError.
See also https://github.com/JuliaLang/julia/issues/7512.
Ivar
kl. 16:03:46 UTC+2 mandag 21. juli 2014 skrev Leah Hanson følgende:
>
> I agree that
I agree that the `["a" "b" "c"]` vs `["a", "b", "c"]` syntax is something
likely to catch new-to-Julia users. I have personally watched people
struggle with that. Programmers familiar with other languages take a bit to
understand the vectors vs row-matrixes thing, when they were just expecting
a li
1. It clearly isn't.
2. It will not cause any overhead in the common case (because it would be a
separate method in Julia). The question is whether this is a case where we
should guess what the user intended, or force the user to fix a potential
problem.
Not sure what we could do about this th
