I lived in a perfect OOP bubble for my entire life. Everything was peaceful and it worked perfectly. When I wanted to move that player, I do player.move(10.0, 0.0); When I want to collect a coin, I go GameMan -> collect_coin(); And when I really need a global method, so be it. I love my C++, I love my python and yes, I also love my GDScript (Godot Game Engine). They all work with classes and objects and it all works perfectly for me.

But oh no! I wanted to learn Rust recently and I really liked how values are non-mutable by defualt and such, but it doesn’t have classes!? What’s going on? How do you even move a player? Do you just HAVE to have a global method for everything? like move_player(); rotate_player(); player_collect_coin(); But no! Even worse! How do you even know which player is meant? Do you just HAVE to pass the player (which is a struct probably) like this? move(player); rotate(player); collect_coin(player, coin); I do not want to live in a world where everything has to be global! I want my data to be organized and to be able to call my methods WHERE I need them, not where they just lie there, waiting to be used in the global scope.

So please, dear C, Rust and… other non OOP language users! Tell me, what makes you stay with these languages? And what is that coding style even called? Is that the “pure functional style” I heard about some time?

Also what text editor do you use (non judgemental)? Vim user here

  • GissaMittJobb
    1·
    9 months ago

    The Player-impl with a self-parameter can only be used together with a Player-struct.

    Example:

    
struct Example {
    field: u8,
}

impl Example {
    fn new(field: u8) -> Self {
        Self {
            field,
        }
    }

    fn get_field(self) -> u8 {
        self.field
    }
}

// Usage
let example = Example::new(1); // doesn't need an instance to be called

let field = example.get_field(); // needs an instance to be called

let field = Example::get_field(example); // equivalent to the previous call

    With reservations for that this code might not compile 100%. Anyway, I hope that clears it up.

    • dukk@programming.dev
      1·
      9 months ago

      BTW: this example probably won’t compile.

      (get_field takes ownership of self and drops it when it goes out of scope. To prevent this, use &self instead).