I am unclear about how higher order parameterizations, some nested, best 
govern method dispatch.
Here is a simplified exemplar.  What of this is appropriate --how is it 
approached?

#=
          n talleys the number of system Floats used as an extended 
accumulator
             F is the floating point type that carries out the smaller ops 
calculations require
                D is the discipline that most immediately benefits from 
this runnable schema 
                   a is a discipline-contextualized abstract supertype of 
... that nests as D{ ϕ }
                      p is a match assignable param that better 
orchestrates multidispatch
=#

immutable StyledFloat{ n, F, D, a, p }
      accum::Vector{F}(n)
      assign::Account{ D{a} }
end

function Glide{ D{a}, p }( context::D{a},  pattern::p ) 
function Glide{ D, a, p }( context::D{a},  pattern::p )


Reply via email to