Clash with BinDeps in definition of |

[kmsquire]

I haven't looked closely, but this might just need to be changed to |>.
(Of course, the same change might be needed in BinDeps...)

julia> using Winston
Warning: New definition 
    |(SynchronousStepCollection,Any) at /home/kmsquire/.julia/v0.2/BinDeps/src/BinDeps.jl:283
is ambiguous with: 
    |(Any,NAtype) at /home/kmsquire/.julia/v0.2/DataArrays/src/operators.jl:502.
To fix, define 
    |(SynchronousStepCollection,NAtype)
before the new definition.
Warning: New definition 
    |(Any,SynchronousStepCollection) at /home/kmsquire/.julia/v0.2/BinDeps/src/BinDeps.jl:286
is ambiguous with: 
    |(NAtype,Any) at /home/kmsquire/.julia/v0.2/DataArrays/src/operators.jl:502.
To fix, define 
    |(NAtype,SynchronousStepCollection)
before the new definition.

[kmsquire]

Sorry, wrong package!

[kmsquire]

(It's BinDeps, not Winston)

[johnmyleswhite]

This sort of thing is going to be a recurring problem for us. Is there any solution we can use other than adding the automatically proposed method? I really don't want to get involved in an "ambiguity-warning prevention" arms race.

Just to be sure, the version of | we're working with really is our OR operator, right?

[simonster]

I don't think we can actually add the proposed definition since we'd need to pull in BinDeps to do it, but since | and other bitwise operators are only really meaningful for integers and arrays of integers, we could make these definitions apply to Integer instead of Any, which would avoid the ambiguity.

[johnmyleswhite]

Totally right. Let's do that.