Ok, I realised that if I make dedup_sorted a generated function I can check what type it is specialising on. It *is* specialising on (Int64,Int64,Float64) but is still not reusing the box for that tuple. But it does work correctly for
immutable Row a::Int64 b::Int64 c::Float64 end On 29 December 2015 at 15:04, Jamie Brandon <[email protected]> wrote: > Hmmm, if I look in the llvm ir for each I can see calling > @julia_dedup_sorted_23928 vs @julia_dedup_sorted_23931 and these are > stable when I recompile f, so presumably those are the cached methods. > If I could somehow grab the ir for those I would have a way to check > whether or not they are being specialised.
