12 ms·
It's actually amazing how many people don't understand that many languages (particularly java) are single dispatch. None of my peers going through university ev
by kevincox 11y ago
It's actually amazing how many people don't understand that many languages (particularly java) are single dispatch. None of my peers going through university even know what the term means and I have been docked marks because the prof computed the answer to a problem as if java supported multiple dispatch. I had to convince the professor to actually compile the code before she believed it. I wonder where this is best taught because it's a really interesting decision of languages yet very few people learn about it.
- klue07 11y agoI run into the same problem. I thought it was because I work in infosec so many people here don't have CS degrees or do a lot of dev work. I don't remember exactly where I learned dispatch, binding, etc. We did have a software dev class where I learned different design patterns. Visitor pattern always blows people's minds when they first see it in action hehe.
- DalekBaldwin 11y agoHow do they get so confused about it? Is it because Java also allows overloading, which is a sort of static multiple dispatch?
- twoodfin 11y agoExactly: foo.bar() has dynamic behavior based on the runtime type of foo. Why shouldn't foo.bar(baz) similarly be able to distinguish the runtime type of baz and pick the 'right' overload? Would it be more surprising to Java newbies if it did work that way?
- kazinator 11y agoBut then, what is the point of foo being associated with the class of bar? Multiple dispatch screams for the abolishment of methods as properties of objects, in favor of generic functions. Youc an still have the syntactic sugar obj.foo(arg), but it basically just translates to foo(obj, arg) where foo is a generic function not associated with foo's class in any way, and obj and arg have equal status. This generic function is what has methods.
- kazinator 11y agoBut then, what is the point of foo being associated with the class of bar? Multiple dispatch screams for the abolishment of methods as properties of objects, in favor of generic functions. Youc an still have the syntactic sugar obj.foo(arg), but it basically just translates to foo(obj, arg) where foo is a generic function not associated with foo's class in any way, and obj and arg have equal status. This generic function is what has methods. Say we implemented "funky" numbers, and would like to implement multiplication of funky and real. When funky is the left argument we get funky.mult(real). If real is no the left, we get real.mult(funky). These functions do the same thing (the multiplication is commutative), yet ... they have to live in separate classes? It is nonsensical. Under generic functions, we just have mult(real, funky) and mult(funky, real) which are methods of the generic mult(whatever, whatever). They both belong to the one generic function: that is the more reasonable organization.
- andrioni 11y agoThat's the way Julia does multiple dispatch, and it works well.
- StefanKarpinski 11y ago> But then, what is the point of foo being associated with the class of bar? One benefit is that the name `bar` is looked up in `foo`'s namespace, which means that it doesn't have to be in the current global namespace. This is a mixed blessing, but it's sometimes what you want.
- kazinator 11y agoThat's an interesting point and basically leads us to "member generic functions". An object has some static slot which is a function, and treated as a method: it can be called obj.meth(args, ...). But, this method is also a generic function. A generic function is a function; an object can have a function, and so an object can have a generic function.
- wtbob 11y agoYou're quite right, but does it make sense to conflate objects and namespaces that way? Might it not make more sense to separate the concerns?
- kevincox 11y agoThat's probably a large component of the problem. It's not unreasonable to expect both methods and overloading to use runtime types. I think this comment sums it up well: https://news.ycombinator.com/item?id=11528588 https://news.ycombinator.com/item?id=11528588
- twoodfin 11y agoI tripped over this as an undergraduate. On the surface, overloading looks like it has the same purpose and function as (virtual) method dispatch, but the difference between static and dynamic typing is subtle enough that they don't interact the way one might expect them to.
- eliben 11y agoThanks for the feedback! This is why I spent a section on showing the "failed attempt". It's surprising how many folks don't understand the difference between overloaded functions (compile-time dispatch) and true multiple dispatch (at run time).
- Splines 11y agoI have to admit, the failed attempt is the first thing I thought of. Thanks for including that and helping me understand why it doesn't work as expected.
- yareally 11y agoI learned about double/single dispatch when I was an undergrad taking a course on design patterns. Trying to wrap my head around the visitor pattern was kind of a pain, but once I saw how it was done in a language that supported double dispatch, it made a lot more sense. Overall, it was one of the more interesting and useful courses I took.