Rust-GPU: Making Rust a first-class language and ecosystem for GPU code

Re:Rust-GPU: Making Rust a first-class language and ecosyste... by Nullabillity on Saturday October 24, 2020 @06:40AM (#24878298)

> It's same issue as in C# and many others: someone has to write and support the bindings, which adds cost.

If C was on the table anyway then you can use bindgen to generate the bindings.

But yeah, safe/native-feeling bindings require someone to go through and annotate everything.

> In VM-based languages which don't use unsafe code, vulnerabilities like this are impossible by design:

The VM itself is still going to have unsafe code at some point.

[ Parent | on HN ]

Re:Rust-GPU: Making Rust a first-class language and ecosyste... by Const-me on Saturday October 24, 2020 @06:47AM (#24878324)

> The VM itself is still going to have unsafe code at some point.

Smaller amount of the unsafe code which is audited, battle-tested, and not extensible by either user nor third-party library developers.

[ Parent | on HN ]

Re:Rust-GPU: Making Rust a first-class language and ecosyste... by creata on Saturday October 24, 2020 @07:00AM (#24878387)

The same could be said of the standard libary vulnerability you linked. But for other code,

(a) that's why people use cargo-geiger.

(b) you're arguing about the very small number of virtual machines that don't give their users such escape hatches.

[ Parent | on HN ]