News for hackers. Stuff that matters.

A comment on Porting a Ray Tracer to Rust, Part 1. Parent comment

Re:Porting a Ray Tracer to Rust, Part 1 by berkut on Wednesday December 31, 2014 @07:02AM (#8819038)
It's quite possible to not use alloca(), but just use C++'s placement new operator to re-use memory already allocated on the stack.

I'm not sure if Rust has something similar to placement new, but I'm sure custom allocators (for memory arenas) are possible in Rust.

[ Parent | on HN ]
Re:Porting a Ray Tracer to Rust, Part 1 by steveklabnik on Wednesday December 31, 2014 @08:24AM (#8819241)
User-defined placement new and custom allocators for existing data structures are still being worked on. `box` can do a form of placement new already, and while you can use your own allocator, you can't use it with already-existing types.
[ Parent | on HN ]
Re:Porting a Ray Tracer to Rust, Part 1 by CyberDildonics on Wednesday December 31, 2014 @08:16AM (#8819210)
That is a valid and useful technique, but being able to dynamically allocate stack memory in the first place is separate from using placement new on stack memory.
[ Parent | on HN ]
Re:Porting a Ray Tracer to Rust, Part 1 by berkut on Wednesday December 31, 2014 @08:19AM (#8819226)
Of course, I was just pointing out it's not always necessary to use alloca - I've written a production-level path-tracer without needing to allocate stack memory dynamically.
[ Parent | on HN ]