ambiguous method definitions in linalg/symmetric

[eschnett]

I build Julia (dev) on OS X from source. I see the warnings shown below during boostrap. Should I worry? I see these warnings on OS X, but not on Linux.

REPLCompletions.jl
REPL.jl
client.jl
printf.jl
util.jl
sparse.jl
sparse/abstractsparse.jl
linalg.jl
Warning: New definition 
    convert could not show value of type Tuple at linalg/symmetric.jl:21
is ambiguous with: 
    convert could not show value of type Tuple at linalg/symmetric.jl:20.
To fix, define 
    convert could not show value of type Tuple
before the new definition.
Warning: New definition 
    convert could not show value of type Tuple at linalg/symmetric.jl:24
is ambiguous with: 
    convert could not show value of type Tuple at linalg/symmetric.jl:23.
To fix, define 
    convert could not show value of type Tuple
before the new definition.
broadcast.jl
statistics.jl
fftw.jl

[stevengj]

I've changed the title of this issue: the real problem here is that linalg/symmetric apparently has some ambiguous method definitions. The "could not show value of type Tuple" is just a symptom: at this stage of the bootstrap process it can't properly output the method signatures, I think.

[stevengj]

cc: @andreasnoack, as git blames you for the lines mentioned above.

[andreasnoack]

Hm. I haven't changed anything in that file for a while but I'll look into it.

[andreasnoack]

I cannot reproduce the ambiguity warnings on neither my Mac or a Ubuntu server. Do you get them if you do make clean;make? Anyone else seeing this?

I don't think you should be worried.

[JeffBezanson]

I got those warnings on the jb/call_constructors branch, and had to fix them here:
https://github.com/JuliaLang/julia/pull/8712/files#diff-10

The warning is technically correct, though pedantic. A better question is why it would happen on some systems and not others.

[timholy]

I've seen it episodically on my own system---most of the time it compiles without issuing that warning, but occasionally it pops up. I'm sure that helps a lot 😄.

Referencing #6187, JuliaImages/Images.jl#76, JuliaImages/Images.jl#59.