At its core, OOP is just commingling data and operations, whereas FP is separating data from operations on data. I’m not an expert at Haskell (I cut my FP teeth on Lisp), but that’s essentially what typeclasses look like to me.
The Rust book has a section on OOP, and the main thing to remember is that Rust solves OOP through composition instead of inheritance. Rust doesn’t have inheritance in any meaningful way, but it can solve problems in a similar way as classical OOP.
i would strongly disagree with that characterization of both fp and oo. classifying rust as oo weakens it imo, and the fact that you can easily solve all the problems oo solves in rust, as your linked document shows, is not proof rust is oo, but rather that oo is unnecessary to solve those problems
object orientation is classes done wrong. typeclasses (and traits) are classes done right
At its core, OOP is just commingling data and operations, whereas FP is separating data from operations on data. I’m not an expert at Haskell (I cut my FP teeth on Lisp), but that’s essentially what typeclasses look like to me.
The Rust book has a section on OOP, and the main thing to remember is that Rust solves OOP through composition instead of inheritance. Rust doesn’t have inheritance in any meaningful way, but it can solve problems in a similar way as classical OOP.
i would strongly disagree with that characterization of both fp and oo. classifying rust as oo weakens it imo, and the fact that you can easily solve all the problems oo solves in rust, as your linked document shows, is not proof rust is oo, but rather that oo is unnecessary to solve those problems
object orientation is classes done wrong. typeclasses (and traits) are classes done right