The hero we need

Hmmm. Maybe I should try that then. Never actually understood why people like these managers as I was always satisfied with the directory tree for organization.

Well maybe besides music. There beets fucking rocks. But in the end I use it also only to sort music into a directory structure.

What’s wrong with just folders and file names?

Where do I complain “the quality” of my opponent? I am trying to understand their viewpoint with regard to non-segregated sports.

I’ve spoken to some athletes about this before – women and men – and I found the opinion that sports should be gender-segregated and that the decision of where trans-athletes should be able to participate in should depend on the specific sport in question.

In my mind good sportsmanship includes fairness and I want to figure out what is “fair” in this situation. Many reasonable people disagree in that regard I think.

Well for many winning and trying their hardest to win is the fun in sport :/

What has this to do with income? It’s also amateur leagues that would be affected.

Well if you don’t do the segregation you will find that in some sports almost no afab people will ever reach the top.

Some sports are of course worse than others in this regard.

And even if there is no physical barrier, historically male dominated sports struggle to find female athletes/players. See for example chess.

How would you solve this?

Also ich würde behaupten, dass es in der Tat nicht sehr cool ist einfach in einer anderen Sprache zu antworten.

You probably have a skewed impression. This is common in some places like Germany, but it’s far from the norm. (Even in Germany it’s mostly telecom that does it for some reason.)

Many ISPs only change the allocated IP only in cases like lost connections and some don’t even do that giving out but not guaranteeing static IPs.

The only way to make Rust segfault is by performing unsafe operations.

Challange accepted. The following Rust code technically segfaults:

fn stackover(a : i64) -> i64 {
    return stackover(a);
}


fn main() {
    println!("{}", stackover(100));
}

A stack overflow is technically a segmentation violation. At least on linux the program recives the SIGSEGV signal. This compiles and I am no rust dev but this does not use unsafe code, right?

While the compiler shows a warning, the error message the program prints when run is not very helpfull IMHO:

thread 'main' has overflowed its stack
fatal runtime error: stack overflow
[1]    45211 IOT instruction (core dumped)  ../target/debug/rust

Edit: Even the compiler warning can be tricked by making it do recusion in pairs:

fn stackover_a(a : i64) -> i64 {
    return stackover_b(a);
}

fn stackover_b(a : i64) -> i64 {
    return stackover_a(a);
}

fn main() {
    println!("{}", stackover_a(100));
}

In assessing risk assume everyone is a bumbling idiot. For we all have moments of great stupidity.

There is definitely a risk in changing it. Many automation systems that assume there is a master branch needed to be changed. Something that’s trivial yes but changing a perfectly running system is always a potential risk.

Also stuff like tutorials and documentation become outdated.

Sie haben gerufen?

That is called racing to sleep iirc and is a valid cpu scheduling technique. It works on the assumption that doing nothing (sleeping is the term there) is much more energy efficient than doing anything even if slowly, so much so that you make up the energy spent to boost to top speed.

I get you peaches, I also just barely survive the emotional coldness of a northern German winter.

A few libraries come to mind immediately: fftw (I think the most widely used fft library) or GMP (I think the most used multi precision library).