Explore Rust in the viewer: a pilot for untrusted-input parsers behind a C ABI; wholesale rewrites later if they clearly help #1602
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#1602
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Exploratory. Where would Rust make the viewer safer, and how do we add it without hurting the build or the C++ codebase?
Why
Memory-safety bugs in C++ show up as crashes users can't report, for example the recent texture-residency heap fault and the startup crash where a device create info was walked after a third party had changed it. Rust's ownership and bounds checks rule out whole classes of them at compile time. AI-assisted work benefits too: the compiler catches more mistakes before they ship. Rust is not faster than C++ by itself; the case for it is safety and maintainability.
Where it makes sense first: untrusted input behind narrow interfaces
Where it does not make sense, for now
The renderer core and anything woven through LL's object model: texture residency, the stores, avatars, the UI. Too wide a boundary for the gain; better C++ ownership, sanitizer runs and tests are the realistic fix there.
Approach
cxx), for example the OSC/VMC parser or the skin import unpacker.cargo-xwinor equivalent).Questions to answer