https://github.com/JuliaLang/julia/issues/7062
> This is the bug I mentioned yesterday where Array{T} reads back as
Array{T, N}.
Array{T} and Array{T,N} describe the same type object
On Sat, May 31, 2014 at 9:01 PM, David Moon <[email protected]> wrote:
> On Saturday, May 31, 2014 1:08:29 PM UTC-4, Iain Dunning wrote:
>>
>> And I don't necessarily think this is wrong - look at the code it
>> generates
>> f{t,n}(::Type{Array{t,n}},::Array{t,n}) at none:3
>> f{t,n}(::Type{Array{t,N}},::Array{t,n}) at none:2
>>
>> There is nothing to distinguish these two from a dispatch perspective -
>> its just picking the one defined last.
>>
>
> n ≠ N
>
> This is the bug I mentioned yesterday where Array{T} reads back as
> Array{T, N}.
>
> Or maybe I didn't understand what you meant by a dispatch perspective.
>
> I checked that reversing the order of the arguments doesn't change this,
> so it's not an issue of the order of resolving static parameters.
>
> Which part of the manual is wrong?
>
>
> The part that says Type{xxx} matches only the object xxx.
>
>
