>>108655159
>theoretically feasible
aka not a problem

File: 1757346283289296.png (33.2 KB)

33.2 KB PNG

>>108655159
>Failing at xir's single selling point

>>108655159
There are cpp related vulns every single day, the fact that you think a rust related vuln is newsworthy tells me everything i need to know.

File: file.png (383.8 KB)

383.8 KB PNG

>>108655159

>>108657345
Rust is sold as a magic bullet and has a community more annoying than that of linux. Completely justified.

File: slowpoke.jpg (7.2 KB)

7.2 KB JPG

>>108655159
>12 dec 25

>>108659255
It isn't though, rust says that your code is safe with the assumption that the unsafe blocks don't contain bugs, it's like an axiom.
If you mess up in unsafe you can still have memory related bugs, but at least there is less surface in which said class of bugs can happen.

Anyway it's not prefect but it's still much better than anything else we have that's still practical to use.

>>108655159
>checks why is this native application using wasm runtime
>it's for plugins
>something that C++ apps just use DLLs for and ask user "do you trust this binary you just downloaded from a basket-weaving forum?" and move on
>meanwhile this Rust app plugins are autmatically sandboxed
Rust wins again.

rust is pointless when you have llms to find your bugs for you

>>108660773
nice bait