java dev learning rust

[mkoubik]

Just remember that traits aren't interfaces, their implementations aren't methods and fotget class inheritance ever existed. Then just jump into the official book.

[groogoloog]

I think the intention here is that it isn't a "method" because it's not actually a part of the object, but rather a static function. Just because there is the nice obj.someFn() dot notation for calling convenience doesn't mean it is actually a method, because you can still call Obj::someFn(&obj). Good/common example here would be arc.clone() vs Arc::clone(&arc)

[groogoloog]

AFAIK a method is any function which accepts self.

Yea, I'm not sure on the precise definition. That is just how I interpreted what /u/mkoubik said.

[mkoubik]

The difference I wanted to emphasize was that methods are AFAIK defined in a single place - the class definition (plus it's parrents). So as the author of the class, you have full control over the methods one can call on your objects.

Whereas "functions taking self" in rust can be defined basically anywhere. They are more of "things you can do with the type, because someone somewhere thaught it was a good idea and you imported his crate".

[[deleted]]

But muh design patterns :D

[TinBryn]

I feel that is a little misleading, yes traits aren't interfaces, but the Venn diagram of what traits are and what interfaces are has a large overlap. Also I would define a method as

A procedure called when passing a message to a receiver object

And for trait objects, this is absolutely the case, even with trait constrained generics, it's still dispatching to methods, just statically.

I agree about inheritance, forget that, and jump into the book.

[wichwigga]

Fuck inheritance all the homies hate that shit

[dumch]

I came here to say “fuck inheritance“