Replying to
@josephguhlin@sci.kiwi
@josephguhlin@sci.kiwi Could you please add the RustLang tag? 🥰
Background: https://fosstodon.org/@mo8it/112056453394255413
Remote
Mo Bitar 
@mo8it@fosstodon.org
mastodon
4.6.6
PhD student in programming language research @ KIT, Germany 💻️
#Rustlings maintainer 🦀
I post about … #RustLang
#Linux
#FOSS
I only follow people with a technical feed. Don't take it personally if I unfollow 🤗
0
Followers
0
Following
6
Posts
Joined November 21, 2022
Website + Blog:
Codeberg:
Posts
Replying to
@MCSpaceCadet@hachyderm.io
@MCSpaceCadet@hachyderm.io @alilleybrinker@hachyderm.io Yes, but bound checking is a huge exception here. Maybe because I have a scientific high performance computing background where you deal with huge vectors and matrices.
Even there: Security and safety by default is a big advantage because when you explicitly opt into skipping bound checks in hot loops, you know for sure where it could blow up and you should check your assumptions instead of debugging the whole codebase when getting wrong results.
Replying to
@tengkuizdihar@mastodon.gamedev.place
@tengkuizdihar@mastodon.gamedev.place @alilleybrinker@hachyderm.io This should answer it:
https://status.codeberg.org/status/codeberg
From my long-term experience: Once in a couple of months they run an announced migration where they have downtimes of a couple of minutes. But you find about it on their official Mastodon account :D
No complaints so far :D
Replying to
@mo8it@fosstodon.org
@alilleybrinker@hachyderm.io You saw me optimize my solutions to Advent of Code in the micro second range. Well, this does sometimes include using an unsafe operation.
But then, I have one unsafe block that I have to deeply study.
During that studying of what can go wrong, you find out that just a character that you don't expect can lead to out-of-bounds reads. But I discovered that while thinking about that single block and its input:
https://codeberg.org/mo8it/advent-of-code-2023/commit/3af95e88ccbf2e2be14d9d9f5ce396b8d3496d43
#RustLang #Rust
Replying to
@alilleybrinker@hachyderm.io
@alilleybrinker@hachyderm.io This is the worst conclusion I ever read…
No, safety and security must be the default!
Yes, it is sometimes required to opt into unsafe operations in Rust to achieve the best performance, especially with bound checks in hot loops.
But you do it explicitly and you are supposed to document why you think it is sane.
You know exactly where it could blow up and you can review that section multiple times instead of having the whole codebase as potentially unsafe…
#RustLang #Rust
Replying to
@alilleybrinker@hachyderm.io
@alilleybrinker@hachyderm.io As always, this is one of the most important aspects of such replies: "Skill issue, just throw more money and education on it"