>Hey rust, can I access my data?
> No.
> Why not?
>there exists a theoretical use case where accessing this data can cause issues.
> Okay, Stack Overflow what do I do?
> Just write 400 lines of code so the pattern can exclusively work with one specific case
> For fricks sake I guess I’ll try. $ Cargo Build & ./target/debug/r-slur.exe
> function panic
> That’s enough of that. Miss me with that software. I code for god now.
Jump in the discussion.
No email address required.
Idk i only understand things v superficially
Ill look into rust and try to de rslur myself
Jump in the discussion.
No email address required.
I mean what you said is 100% right, I just really wanna know wtf the other guy meant when he said "restricted"
Jump in the discussion.
No email address required.
I understood it as constrained by 3rd party libraries or so obfuscated u had to trust the code, lik3, setting u up for.mitm vectors but idk
E:
I guess what i mean is that C can do anything and everything, certain iterations do processor interrupts and direct memory addressing. U could feasibly write an entire OS in C including networking protocols
If a codebase made decisions for u, like, preventing certain functions or variables from executing in the name of "security" w/o clear documentation i could see it being restrictive
Jump in the discussion.
No email address required.
More options
Context
More options
Context
More options
Context