Too complicated. Just enter a negative number.

It actually is possible to segfault in safe Rust, although it is considered a bug. Proofs of concept are shown in this cve-rs crate.

If you want an explanation of why this happens, I recommend this video: https://youtu.be/vfMpIsJwpjU

Never underestimate a dedicated community to make anything competitive

Imagine getting segmentation faults at runtime

This post was brought to you by the Rust crew

Rust borrows a lot of it’s design from functional programming languages like Haskell, which has its good and bad. You could also choose to implement this behavior iteratively like typical C programs, but that tends to be ugly in other ways.

Personally, I’ve grown fond of the functional style. You see it in other places too, like the higher order functions in JavaScript. What’s good about them in Rust is you still get amazing performance due to zero-cost abstraction. Trying to implement it yourself would likely be slower, so use them any chance you get.

I regularly use wireless earbuds, which are extremely convenient, but I am not looking forward to the day when the battery is insufficient for me and I can’t replace it due to “innovation”. I also miss out on having splitters so that 2 people can listen to the same audio. I know Bluetooth LE is supposed to fix that, but I don’t even know what devices support that. Like others said, having the choice is important, but Apple’s “bravery” and market domination removed that from us…

Here is their POC in Python:https://github.com/JJTech0130/pypush

And their article explaining it: https://blog.beeper.com/p/how-beeper-mini-works