Somewhere smaller than a tiger, that would win 100% of the time. I’d guess 30 lbs is where things start to get serious

What sublinks mess? I’m out of the loop on that

This is a great place to post it IMO. Helps keep the community active

Double curly is pretty common IME, but I have more experience in backend which is less likely to be involved in an error like this. Off the top of my head, handlebars, django, and jinja2 all use that style.

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 that 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 more succinct error handling if you’d like.

EDIT: Here’s also a version using anyhow for error handling, and the aforementioned Result collecting:

use anyhow::{anyhow, Result};

fn main() -> Result<()> {
    let text = "seeds: 79 14 55 13\nwhatever";
    let seeds: Vec<u32> = text
        .lines()
        .next()
        .ok_or(anyhow!("No first line!"))?
        .split_whitespace()
        .skip(1)
        .map(str::parse)
        .collect::<Result<_, _>>()?;
    println!("seeds: {:?}", seeds);
    Ok(())
}

Every Single Scandinavian Crime Drama

The ideal solution is not a Netflix monopoly, it’s one where content providers must pick a single price, and any streaming service can pay that price and provide access to the content. That way you can pay for only Netflix, but get access to everything. Netflix wouldn’t end up with a monopoly though, because anybody else could offer a better service and people could switch to it and not lose access to anything.

This is unlikely to happen anytime soon due to the intentional clusterfuck of laws like copyright, but it would solve the problem neatly.

You probably wouldn’t be committing this, unless you’re backing up a heavily WIP branch. The issue is that if you’re developing locally and need to make a temporary change, you might comment something out, which then requires commenting another now-unused variable, which then requires commenting out yet another variable, and so on. Go isn’t helping you here, it’s wasting your time for no good reason. Just emit a warning and allow CI to be configured to reject warnings.

That’s 👏 what 👏 CI 👏 is 👏 for

Warn in dev, enforce stuff like this in CI and block PRs that don’t pass. Go is just being silly here, which is not surprising given that Rob Pike said

Syntax highlighting is juvenile. When I was a child, I was taught arithmetic using colored rods. I grew up and today I use monochromatic numerals.

The Go developers need to get over themselves.

It was actually Sonic