Day 9: Mirage Maintenance

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • Code block support is not fully rolled out yet but likely will be in the middle of the event. Try to share solutions as both code blocks and using something such as https://topaz.github.io/paste/ , pastebin, or github (code blocks to future proof it for when 0.19 comes out and since code blocks currently function in some apps and some instances as well if they are running a 0.19 beta)

FAQ

🔒 Thread is locked until there’s at least 100 2 star entries on the global leaderboard

🔓 Unlocked after 5 mins

      • morrowind@lemmy.ml
        3·
        11 months ago

        I guess I’ll have to take rustaceans who claim they’re more productive in rust than python seriously now

      • Sekoia@lemmy.blahaj.zone
        3·
        11 months ago
        1. Setting up boilerplate beforehand, I only need to fill in the functions (and the return types)
        2. Really good parsing library (aoc_parse). Today my entire parsing code was parser!(lines(repeat_sep(i64, " ")))
        3. Iterators! Actually really ideal for AoC, where pipelines of data are really common. Today both the main part (sum of lines) and inner part (getting a vec of differences) can be done pretty easily through iterators

        Today was pretty ideal for my setup. In general I think Rust is really good for later days, because the safety and explicitness make small mistakes rarer (like if you get an element from a HashMap that doesn’t exist, you don’t get a None later down the road (unless you want it, in which case it’s explicit), you get an exception where it happened.

        I just really like Rust :3