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 tlamponi on Saturday October 24, 2020 @07:46AM (#24878585)

> Rust parallism guarantees are only applicable to threaded code and internal resources.

No, it can apply for single threaded async stuff as well.

> One way that Rust compiles way slower than C++ is its Gentoo approach to libraries.

That's not true in at least two ways:

1. You can also produce shared libraries in rust, I know as we do so for some stuff.

2. C++ often has some much stuff in headers that you do not only compile your code..

Also, in my experience, the compile time is nonetheless (faster to slower):

1. C

2. Rust

3. C++

if one is doing a mid-sized or bigger project with lots of language features used.

[ Parent | on HN ]

Re:Rust-GPU: Making Rust a first-class language and ecosyste... by pjmlp on Saturday October 24, 2020 @10:01AM (#24879274)

Single threaded async is a special case of M:N threading model.

Shared libraries in Rust don't get distributed via cargo like Conan, vcpkg or OS package managers are capable of.

Too much C++ stuff in headers, yes that is a thing, specially in badly organized builds. Extern templates, incremental compilation and linking are also a thing, and VC++ already has experimental C++20 module support.

My dummy Gtk-rs test project to validate Rust improvements after each release takes 16 minutes currently on a core duo with 8 GB and SSD. The Gtkmm variant takes about 3 minutes, because it doesn't need to compile Gtk-rs on each compiler upgrade.

[ Parent | on HN ]