Is this for real? If so how is Rust not a complete joke?pic.twitter.com/Zz52Hg6R9q
Yeah, I do @musllibc, FOSS & infosec stuff. But now is not the time for a mostly-/only-tech Twitter feed.
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
Is this for real? If so how is Rust not a complete joke?pic.twitter.com/Zz52Hg6R9q
okay, what else can you do in an OOM condition *that makes sense to do*, in pretty much any case?
Return (or throw, if that's your idiom) the error to the caller, leaving any mutable objects being manipulated in consistent (preferably unmodified) state.
And 99% of the time the caller will either abort or ignore the error and SIGSEGV anyway.
N levels back up, maybe. Unless it's stateless/contains no valuable state, or unless it's utter crap, not without first dumping a recovery file of some sort.
Or you can write rust with nostd, and no allocator (bring your own). But what would you do anyway if you `vec.push(x)` and somehow there isn't enough ram? How would you signal the error in a way that makes sense to the caller of `push`?
The push method could return `Ok(())` when it succeeds and `Err(x)` when it fails. Since `Result<T, U>` is marked #[must_use], it forces the caller to handle the error case. Rust as a language is well-suited to writing low-level, robust code. The non-core stdlib is the issue.
im really thinking like 87% of rust users woulda revolted if they'd had to error-handle every allocation
Writing correct code is hard. Everyone wants toy languages that let you pretend it's not and paper over everything that could go wrong. *sigh*
I'd argue a lot of the time, handling OOM conditions without unwinding does not get you the most correctness per unit effort spent
I think "correctness per unit effort spent" is a bogus metric. In a better model, you start from a correct trivial program and build up, constrained by not knowingly making it incorrect.
So the choice isn't spending effort to make it correct or not. The choice, given fixed effort, is implementing more functionality incorrectly or less functionality correctly.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.