Viewing profile — yourdetect
yourdetect
HN member- Joined
- Thu, Dec 18, 2025, 8:51 AM UTC
- HN karma
- 7
- Public activity
- 11 items
- HN profile
- View on Hacker News ↗
About yourdetect
No profile information was provided.
Recent public activity
-
comment
Comment #46324638
> Of course, this bug was in an `unsafe` block, which is exactly what you would expect given Rust's promises. The fix was outside of any Rust unsafe blocks. Which confused a lot of…
-
comment
Comment #46324619
I think defining terminology here might help. An attempt: Language-UB (L-UB): UB according to the guarantees of the language. Project-compiler-UB (PC-UB): The project picks compile…
-
comment
Comment #46324580
[flagged]
-
comment
Comment #46323627
I am very wary of going that route. If there is undefined behavior, the compiler is in principle allowed to do anything and everything, unless it promises something beyond what the…
-
comment
Comment #46323579
[flagged]
-
comment
Comment #46323527
> Should we remove C or Your post is curious, for the post I quoted basically argued for just that eventuality for all new code. Even as the new language introduces undefined behav…
-
comment
Comment #46323474
[flagged]
-
comment
Comment #46323456
[flagged]
-
comment
Comment #46322554
From the comment section: > To me the more salient questions are how long before (a) we get Rust in a core subsystem (thus making Rust truly _required_ instead of "optional unless …
-
comment
Comment #46310473
Does this contain unsafe? Even the Linux kernel's Rust code have memory safety bugs. https://news.ycombinator.com/item?id=46309536
-
comment
Comment #46310351
It's UB, it is not memory safe, so in theory, and often also in practice with this specific kind of bug, absolutely anything could happen, including code execution. Greg Kroah-Hart…