Re:Julia's multiple dispatch explained with Pokemons
by pjmlp on Wednesday July 21, 2021 @08:47AM
(#27905529)
That is method overloading, which isn't the same as multi-dispatch.
Re:Julia's multiple dispatch explained with Pokemons
by ThomasMoll on Wednesday July 21, 2021 @01:02PM
(#27908913)
Groovy supports multi-dispatch, if you needed to encapsulate a generic type, the compile would dynamically resolve that type correctly. See my example in Java (which has method overloading, but not MD)
Re:Julia's multiple dispatch explained with Pokemons
by brabel on Wednesday July 21, 2021 @12:52PM
(#27908748)
What would multi-dispatch do differently???
Re:Julia's multiple dispatch explained with Pokemons
by adgjlsfhk1 on Wednesday July 21, 2021 @06:42PM
(#27913093)
the difference is that overloading works on compile time types but dispatch works on runtime types. This matters because when you write a generic algorithm, you don't know the type, so don't get the right behavior with overloading (you get the generic fallback).
Re:Julia's multiple dispatch explained with Pokemons
by brabel on Thursday July 22, 2021 @07:00AM
(#27917480)
In Groovy, dynamic dispatch is used. It's the runtime types that matter, as my example makes patently clear.
EDIT: to make it even more obvious there's no difference:
class Fire{}
class Water {}
class Grass {}
class Ice {}
def eff(Fire f, Grass g) { 'burn' }
def eff(Fire f, Ice ice) { 'melt' }
def eff(Water w, Grass g) { 'grow' }
def eff(Water w, Ice ice) { 'freeze' }
def eff(a, b) { 'undefined' }
// hide compile-time types
Object fire = new Fire()
Object grass = new Grass()
Object ice = new Ice()
Object water = new Water()
println eff(fire, grass)
println eff(fire, ice)
println eff(water, grass)
println eff(water, ice)
println eff(ice, water)
Prints: burn
melt
grow
freeze
undefined
burn melt grow freeze undefined