News for hackers. Stuff that matters.

A comment on Which language has the brightest future for replacing C: D, Go, Rust?. Parent comment

Re:Which language has the brightest future for replacing C: ... by kibwen on Wednesday November 11, 2015 @06:31AM (#10546082)
Rust's libcore wasn't split out for "LOL, memory is finite" domains. It exists so that you can write Rust programs that restrict themselves to doing no dynamic allocation whatsoever, as needed for environments where an allocator simply isn't available or allowed.
[ Parent | on HN ]
Re:Which language has the brightest future for replacing C: ... by quotemstr on Wednesday November 11, 2015 @06:37AM (#10546103)
My point is that I want to write programs that do use dynamic allocation, but also handle failure of this dynamic allocation in a reasonable way. Right now, Rust's philosophy is that you can choose whether to use dynamic allocation, but if you do, it'd better be an infallible allocator.
[ Parent | on HN ]