• Jestzer@lemmy.world
    link
    fedilink
    arrow-up
    20
    ·
    edit-2
    1 day 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@lemmy.zip
      link
      fedilink
      arrow-up
      6
      ·
      1 day 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 }) }

  • Frezik@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    2
    ·
    1 day 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.

  • ZILtoid1991@lemmy.world
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    1 day 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@lemmy.today
      link
      fedilink
      arrow-up
      25
      ·
      1 day 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