What could go wrong trying to solve AoC in Rust?

Comments

• m_f@midwest.social ⁨11⁩ ⁨months⁩ ago

  The collect’s in the middle aren’t necessary, neither is splitting by ": ". Here’s a simpler version

  fn main() {
      let text = "seeds: 79 14 55 13\nwhatever";
      let seeds: Vec<_> = text
          .lines()
          .next()
          .unwrap()
          .split_whitespace()
          .skip(1)
          .map(|x| x.parse::<u32>().unwrap())
          .collect();
      println!("seeds: {:?}", seeds);
  }
  

  It is simpler to bang out a [int(num) for num in text.splitlines()[0].split(’ ')[1:]] in Python, but just shows the happy path with no error handling, and does a bunch of allocations that the Rust version doesn’t. You can also get slightly fancier in the Rust version by collecting into a Result for better error handling and all that.

  source

  • MaliciousKebab@sh.itjust.works ⁨11⁩ ⁨months⁩ ago

    Yeah I was trying to do something like reading the first line by getting an iterator and just looping through the other lines normally, since first line was kind of a special case but it got messy quick. I realized halfway that my collects were redundant but couldn’t really simplify it. Thanks

    source
  • sukhmel@programming.dev ⁨10⁩ ⁨months⁩ ago

    Also, anyhow::Context provides a convenient way to turn Option<T> and Result<T, Into<anyhow::Error>> into anyhow::Result<T>

    Like this:

    use anyhow::Context;
    
    // to my understanding it's better to 
    // specify the types when their names 
    // are the same as in prelude to improve
    // readability and reduce name clashing
    fn main() -> anyhow::Result<()> {
        let text = "seeds: 79 14 55 13\nwhatever";
        let seeds: Vec<u32> = text
            .lines()
            .next()
            .context("No first line!")?     // This line has changed
            .split_whitespace()
            .skip(1)
            .map(str::parse)
            .collect::<Result<_, _>>()?;
        println!("seeds: {:?}", seeds);
        Ok(())
    }
    

    source
• Schmeckinger@lemmy.world ⁨11⁩ ⁨months⁩ ago

  You can’t really blame that on rust.

  source

  • MaliciousKebab@sh.itjust.works ⁨11⁩ ⁨months⁩ ago

    Yeah ngl it’s very ugly. But hey as long as it works it’s not stupid amirite?

    source

    • xlash123@sh.itjust.works ⁨11⁩ ⁨months⁩ ago

      Rust borrows a lot of it’s design from functional programming languages like Haskell, which has its good and bad. You could also choose to implement this behavior iteratively like typical C programs, but that tends to be ugly in other ways.

      Personally, I’ve grown fond of the functional style. You see it in other places too, like the higher order functions in JavaScript. What’s good about them in Rust is you still get amazing performance due to zero-cost abstraction. Trying to implement it yourself would likely be slower, so use them any chance you get.

      source
• GeniusIsme@lemmy.world ⁨11⁩ ⁨months⁩ ago

  Show the alternative, I’ll have a good laugh.

  source

  • janAkali@lemmy.one ⁨10⁩ ⁨months⁩ ago

    It’s Nim, but I really doubt you can’t do this in Rust:

    var seeds = lines[0].split(":")[1].splitWhitespace().mapIt(it.parseInt)
    

    Full solution: codeberg.org/Archargelod/…/solution.nim

    source

    • GeniusIsme@lemmy.world ⁨10⁩ ⁨months⁩ ago

      Ahh, it is the same thing. Rust example surely has some cruft, but mostly for the better. I’m sure not all of it is needed.

      source
• chinstrap@lemmy.ml ⁨11⁩ ⁨months⁩ ago

  Java 2. World is full of wonders

  source

  • crispy_kilt@feddit.de ⁨11⁩ ⁨months⁩ ago

    Java 2 didn’t have streams nor iterator combinatorics, not sure what you mean?

    source

    • chinstrap@lemmy.ml ⁨11⁩ ⁨months⁩ ago

      i didn’t mean as a version. I meant as overuse of streams

      source

      • -> View More Comments