„Claude, rewrite the Linux kernel in Rust. Make no mistakes.“

I love that series.

What you are doing here is called reversal of victim and perpetrator roles.

Some People are assholes with asshole opinions forcing their asshole opinions upon you and your dog

Gerne! :-)

There is a trope of nonsensically combining statements, e.g. "at night it's colder than outside" (it's called Alogismus - is alogism a proper english word?). It's children humor, most of them find it funny somewhere between 6 and 14 yo.

This sentence is an example of that:

• camels don't sit in basements
• you can't chop kerosene
• Christmas has nothing to do with the fact that the camel traveled via bicycle

Another pointer I can look for. Thank you :-)

yeah, he is for sure. I didn't want to question this classification.

context: I'm a German.

Is this some American nazi code? In Germany this is just the word for weapon.

I'm seriously curious.

It is Rust implementing the pattern. So... :P

When people say "async is viral" in Rust, they mean that once you make one function async, that change tends to ripple through the rest of your code. Any function that calls it usually has to become async as well so it can await the result. In turn, the callers of those functions often need to become async too.

This propagation can continue all the way up the call stack until you reach your application's entry point. The main exception is when you introduce an explicit synchronous-to-asynchronous boundary, such as by using block_on, which drives the future to completion without requiring the caller itself to be async.

• viral async
• viral lifetime annotations

🫣