News for hackers. Stuff that matters.

A comment on Why is Rust difficult?. Parent comment

Re:Why is Rust difficult? by pjmlp on Monday January 22, 2018 @08:37AM (#16204206)
Well, declaring untraced references in Modula-3 or Active Oberon, or doing native heap allocations in Nim, D, Java and C# is relatively simple.

Using GC languages doesn't mean doing 100% memory allocation via GC.

[ Parent | on HN ]
Re:Why is Rust difficult? by lmm on Monday January 22, 2018 @09:03AM (#16204367)
I've done it in Java; it's not officially supported in the language standard (or has only recently been added if so - certainly they were talking about it for years), and the wider language does not generally have the support or idioms you would want (e.g. try-with-resources was only introduced a couple of versions ago), libraries aren't oriented towards that style.... It's certainly doable but I'd stand by it not being easy or natural.
[ Parent | on HN ]
Re:Why is Rust difficult? by pjmlp on Monday January 22, 2018 @09:46AM (#16204678)
Although I mentioned Java, due to ByteBuffers and Unsafe, it is clearly not the best one of the set of languages that I mentioned.

Others on that list have specific language features for GC free allocation.

[ Parent | on HN ]