• @Jestzer@lemmy.world
    22•5 days ago

    I just realized that the 2 characters in the back of the truck originally aren’t there, and then they randomly appear. It’s in the original episode too.

    • display_name
      7•5 days ago

      I’m trying to come up with a good pun how ownership and safety could have prevented this but…

      use std::sync::OnceLock;

      #[derive(Debug)] struct BrainCell { in_use: bool, }

      static BRAIN_CELL: OnceLock<BrainCell> = OnceLock::new();

      fn get_brain_cell() -> &'static BrainCell BRAIN_CELL.get_or_init(| { println!(“Allocating brain power… this might take a while.”); BrainCell { in_use: true }) }

  • FrezikEnglish
    9•5 days ago

    “You just don’t understand strong typing” when the problem at hand is about lifetimes.

    I’m glad the Rust compiler is super helpful, because the community isn’t.

    • OpenStarsEnglish
      8•5 days ago

      Must be related to dat der “memory safety” they keep talkin bout.

  • @ZILtoid1991@lemmy.world
    6•5 days ago

    Would be better at illustrating Rust’s cultiness if it were instead “Rust is not FP, you can opt out of it, and const by default is just good practice”.

    • Traister101
      25•5 days ago

      I mean should const not be the default? I do want to mutate objects sometimes but usually I just need a view of it’s state and not write access. It also makes mutable data a lot more obvious if whoever wrote the code your reading wasn’t putting const on stuff they should have been. Seems like something all languages with const semantics should have done