3 ms·
> The traditional solution is to have different languages for different code layers Isn’t the rust solution to wrap Q&D/experimental code in “unsafe {}”? I thi
by Someone 4y ago
> The traditional solution is to have different languages for different code layers
Isn’t the rust solution to wrap Q&D/experimental code in “unsafe {}”? I think that’s superior for the parts where you don’t need the fast iterations of an interpreter.
- flohofwoe 4y agoNot sure, I haven't tried Rust for gamedev stuff. But I think unsafe{} is still very picky. It just removes some borrow checker restrictions, but still requires a lot of 'correctness', and I guess it also doesn't magically improve compilation time. One other 'modern' solution is to use a compiled language for the whole 'stack', but with a hot code reload solution, so you can change the code on the running game - which also tremendously reduces turnaround times.