Why you should, actually, rewrite some of it in Rust

Re:Why you should, actually, rewrite some of it in Rust by AnimalMuppet on Wednesday July 12, 2017 @12:28PM (#14753901)

Minor nit: I believe that you can get memory allocators that provide upper bounds of execution time. But it won't be the default allocator in most languages. Also, you need an allocator that cannot ever fail to return a valid block. Even if you have all that, it still makes it much harder to prove that your worst-case timing is fast enough.

So, yeah, no allocations in situations like that. Allocate at start-up, and re-use your buffers (for that kind of code).

[ Parent | on HN ]

Re:Why you should, actually, rewrite some of it in Rust by hashmal on Thursday July 13, 2017 @09:11AM (#14760923)

I think there are memory allocators that provide bounds, yes, but I never bothered finding one. Time-constrained code is so demanding already that handling the memory part is just one drop in an ocean of constraints. (and the whole thing is actually very interesting to do!)

[ Parent | on HN ]