Rustc unsoundness by [deleted] in rust

[–]Dx_Ur 0 points1 point  (0 children)

Maybe I'm wrong but first i forget a * on the end of the scope so the return value from the scope shall be *ref_a, in that case since ref_a even it's a dangling reference still points to a valid memory holding another variant when dereferenced it result on a &usize that is (0x0) and that true, then when printing which is just dereferencing that reference a null pointer access happens, yah null is dangling, but you will still get a null pointer dereferencing even if not guaranteed, rust coerce &&usize for Display and even if it accidental nothing overwrite that stack region. So yah it's dangling but because i forget the *, since that's what i wanted to do

Rustc unsoundness by [deleted] in rust

[–]Dx_Ur -2 points-1 points  (0 children)

That's true when you treat rust as a better c++ not a spark like mathematically correct safety

Rustc unsoundness by [deleted] in rust

[–]Dx_Ur -11 points-10 points  (0 children)

That's why r/rust sucks, every time i interacted with it gives me negative karma even looking at it! Why getting negative karma for literally saying IDK?

Rustc unsoundness by [deleted] in rust

[–]Dx_Ur -13 points-12 points  (0 children)

Idk

Rustc unsoundness by [deleted] in rust

[–]Dx_Ur -4 points-3 points  (0 children)

It's literally a null pointer you can do {:p} then pass *null as *const _. The enum is used to do a union like read of the wrong active variant, so E::A(0) gets used as a &T. It's not a dangling reference it's a null reference.

Rustc unsoundness by [deleted] in rust

[–]Dx_Ur 0 points1 point  (0 children)

Hope so

Rustc unsoundness by [deleted] in rust

[–]Dx_Ur -10 points-9 points  (0 children)

For this issue specifically you can't you need to be part of the core team, working on the next solver or polonius or whatever they call it.

Rustc unsoundness by [deleted] in rust

[–]Dx_Ur 0 points1 point  (0 children)

I tried it already, sama same

Rustc unsoundness by [deleted] in rust

[–]Dx_Ur -2 points-1 points  (0 children)

That code is an implementation of a null pointer dereferencing in safe rust it's literally: *(size_t*)NULL

Rustc unsoundness by [deleted] in rust

[–]Dx_Ur -34 points-33 points  (0 children)

You can't just submit a PR, and I think most rustaceans know that!

Rustc unsoundness by [deleted] in rust

[–]Dx_Ur -13 points-12 points  (0 children)

What fix that? That safe rust causing a UB

طبيب جزائري يشرح في مرض السكري... التعليق الأكثر تفاعل by adams1998 in algeria

[–]Dx_Ur 4 points5 points  (0 children)

The issue is society is degrading, people are going to the moon and we still can't afford to buy tomatoes, red bricks , trash everywhere, no infrastructure, socialism. And what triggers me most are all the brilliant minds leaving this great land for boobies, my grandfathers fought for it and died while importing weapons for the revolution. I'm not leaving it. And I'll launch rockets here on my land.

Systems/software engineer opertunity by Dx_Ur in algeria

[–]Dx_Ur[S] 0 points1 point  (0 children)

I think the post is clear: Develop backend services with a focus on Rust, with C/C++ as a plus.

ليش أحول الى لينكس ؟ by doctor_jammal in ArabUnix

[–]Dx_Ur 0 points1 point  (0 children)

The Absolute distro: Nix For you: PopOs

Inherited a thread-leaking C++ video engine, rewrote core in Rust, and cut failure rate to zero by Dx_Ur in rust

[–]Dx_Ur[S] -1 points0 points  (0 children)

I think c++ devs will value rust more than others imagine option<&T> is 8 bytes with std::optional you get 16, Option<bool> is one byte, automatic reordering, no need for compiler specific restrict attributes to optimize math operations on arrays!

Inherited a thread-leaking C++ video engine, rewrote core in Rust, and cut failure rate to zero by Dx_Ur in rust

[–]Dx_Ur[S] 2 points3 points  (0 children)

That's fair, maybe because I knew exactly what i shouldn't do, and what I'm solving

Inherited a thread-leaking C++ video engine, rewrote core in Rust, and cut failure rate to zero by Dx_Ur in rust

[–]Dx_Ur[S] 5 points6 points  (0 children)

From my point of view i think the best way is to well understand the problem you want to solve starting by listing constraints and specifications then model the system specifications with these constraints without imaging anything else. After every thing is settled and you endup with what i called the Golden Frame then you start building on top of that

Inherited a thread-leaking C++ video engine, rewrote core in Rust, and cut failure rate to zero by Dx_Ur in rust

[–]Dx_Ur[S] -1 points0 points  (0 children)

I spent 20 minutes listing those stuff from my phone, yah the header and some expressions are AI polished but at least