A post that lists several troubles in using Rust to write raytracer:
Regarding the "Difficulty of expressing mutable array access" it says:
This makes it a bit annoying to write a tile-based instead of row or pixel-based tracer.<
Perhaps a safe abstraction like a 2D version of slice::split_at_mut could be written in that raytracing code.
Isn’t the API provided by ndarray enough for this?
1 Like
system
Closed
3
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.