I thought that goes without saying.

Ignore the reasonable comments that say you are more than ready.

The next step is obviously learning Haskell, specifically sum types (like rusts enums), lists (lazy, like rusts iterators) and classes (like rusts traits).
Then you will think, “if only there was a language that was a mix of C and Haskell” and that’s rust.

-u would give you the space back.
The ransomware doesn’t. There is a block of data, sitting there, taunting you.

Hebrew-based content appears machine-translated

Did they vibe code their false identity as well?

Spectre, because it forces us to acknowledge the abstractions we build upon.

2Gb well spent

You can design a language where you don’t need to generate code to accomplish this.

Other people have python scripts generate C, so having on in the same codebase and language is certainly an improvement.

My question isn’t why this is necessary in Rust. My question is why Rust was designed such that this was necessary.

Because otherwise the compiler team either also needs to maintain a huge amount libraries or cut corners and move things to runtime that really should happen at compile time.

Someone mentioned elsewhere that this allows for compile-time type safety. I’m still trying to wrap my head around how that works.

printf is a great example. According to the C type system, it takes a string and a variable amount of untyped arguments dependent on the content of the string, but that doesn’t actually describe the allowed arguments.
Misusing printf like this printf("%s", 42); will get you a warning, but only because there is a special case for printf in the compiler. If you have your own function that does the same as printf, and you misuse the same way, you will find out by dissecting the core dump.

In rust the format string gets parsed at compile time by a macro, which decides the type of each arguments that can than be checked by the compiler. Imagine printf(“%s %d”,…) created a function with the signature specialized_printf(char* agr0, int arg1), it would be impossible to pass the wrong types of arguments.

Now that these tools exist people have gone further and made a library that checks SQL queries against the shema of a running database and causes a compile error if it doesn’t fit.

While your partner can’t be found by it, they can be approximated to an arbitrary degree of precision.

Lure the bugs to your screen and catch them or let them hide in the shade. That’s the choice.

The default configuration in 2017 was public write access, but those databases where taken over long ago.

Rust doesn’t have a scheduler.
The issue is the false assumption, that the remove operation can safely be done without taking a lock. This can be done in some specific data structures using atomic operations, but here the solution was to just take the lock. The same thing could have happened in a C code base but without the unsafe block indicating where to look for the bug.

The commenter must believe forks are magic.

and like half the [rust] devs left for Crab.

Crablang is a joke fork to make fun of a trademark screw up by the rust foundation.

Exactly, you never know when you want to change the base for printing out from under someone.

What unholy mix of languages is that? It is dominated by a blend of javascript and python, but with notes of something exotic. Maybe algol? or vhdl?, there is to little to tell.
Impressive, someone write up a spec and publish it to the esolang wiki.

The code seems to be C-style language with curly braces and types in front for variable declarations, probably java. This means the variable must be declared of screen before the loop or it would not compile. It could have a previous value or be uninitialized, but that does not affect the end result.

Segmentation fault, you forgot to take the reference and derefenced a null pointer.

Because the only brainfuck instructions in your comment where a - which decrements and 20 +, each of which increments.
Mine echos the first two characters from stdin, because of the commas and dots.

SerenityOS is “a love letter to '90s user interfaces with a custom Unix-like core”.
It’s good enough to be proud of, while alienating normal people, not incidentally, like linux used to, but on purpose, like this sentence does, making it a great for elitists.

Spotify suck at programming. When using the app offline, I can view and play songs and podcasts directly or from the queue, but the menu to add stuff to the queue doesn’t load.

No self respecting linux vegan would proselytizes for Bitcoin. They might begrudgingly use them for their original purpose, but if asked about electronic payment, they talk about gnu taler.