Re: [julia-users] How to determine which functions to overload, or, who is at the bottom of the function chain?

I hadn't thought of using the debugger to step through and see where a function call ends up. That is a great idea. Thanks, Colin On Tuesday, 18 October 2016 02:01:43 UTC+11, Patrick Belliveau wrote: > > I would add the general comment that in julia 0.5 you can use Gallium to > step into a

Re: [julia-users] How to determine which functions to overload, or, who is at the bottom of the function chain?

I would add the general comment that in julia 0.5 you can use Gallium to step into a call to a base function and explore what's actually being called. For the .< example, from the julia prompt: using Gallium @enter 0.4 .< 0.5 @enter 0.4 .< 0.5 In operators.jl:159 158 .!=(x::Number,y::Number)

Re: [julia-users] How to determine which functions to overload, or, who is at the bottom of the function chain?

This was a very helpful answer. Thank you very much for responding. Cheers, Colin On 16 October 2016 at 20:23, Milan Bouchet-Valat wrote: > Le samedi 15 octobre 2016 à 20:36 -0700, colintbow...@gmail.com a > écrit : > > Hi all, > > > > Twice now I've thought I had

Re: [julia-users] How to determine which functions to overload, or, who is at the bottom of the function chain?

Le samedi 15 octobre 2016 à 20:36 -0700, colintbow...@gmail.com a écrit : > Hi all, > > Twice now I've thought I had overloaded the appropriate functions for > a new type, only to observe apparent inconsistencies in the way the > new type behaves. Of course, there were no inconsistencies.

[julia-users] How to determine which functions to overload, or, who is at the bottom of the function chain?

Hi all, Twice now I've thought I had overloaded the appropriate functions for a new type, only to observe apparent inconsistencies in the way the new type behaves. Of course, there were no inconsistencies. Instead, the observed behaviour stemmed from overloading a function that is not at the