Change a<b, max(a,b) to a.<b, max.(a,b)

[dlfivefifty]

The current usage is confusing as you'd expect < to return a Bool. I think overloading .< would be better.

This will have to wait til 0.4 support is dropped

[dlfivefifty]

Hmm, realized a::Fun < b::Fun isn't implemented. This could be defined as 0 < b-a. And then a .< b would return a Fun that is piecewise true/false.

[dlfivefifty]

I think the issue with max(a::Fun,b::Fun) is one would expect it to return either b or a. Where max.(a,b) is clear that you want the pointwise definition

[dlfivefifty]

Oh, but in 0.5 there is still autofusing:

julia> max([1,2,3],[0,5,6])
3-element Array{Int64,1}:
 1
 5
 6

[dlfivefifty]

max([1,2,3],[0,5,6]) now throws a deprecation warning, so I think the same should be true for Funs.