News for hackers. Stuff that matters.
Re:Rust concurrency: the archetype of a message-passing bug by mratsim on Tuesday June 23, 2020 @06:08AM (#23611905)
> How come it does not get as much attention as Rust when it comes to safety?

Community building.

That said, Nim is very much inspired by Ada for the future safety features, in particular Z3 integration to enable Spark-like use-cases

- https://nim-lang.org/docs/drnim.html

AFAIK Ada was also inspired by Rust for memory-related safety. I find the cross-pollination between languages fascinating.

WHat's the multithreading story of Ada like? I didn't find that much code or article or papers when I was searching for multithreading runtime in other languages.

Re:Rust concurrency: the archetype of a message-passing bug by micronian2 on Wednesday June 24, 2020 @11:04PM (#23636467)
Hi,

Actually, it is the pointer support in the SPARK variant of Ada that was inspired by Rust's ownership/borrower semantic. Originally, SPARK didn't allow any pointer usage, but with the new ownership/borrower semantics, SPARK allows limited usage of Ada pointers.

As for more literature about using Ada's tasking features, I recommend the wonderful books and papers by Alan Burns and/or Andy Wellings, such as "Concurrent and Real-Time Programming In Ada (3rd Edition)." AdaCore has an old presentation on using Ravenscar with multi-core processors (https://people.cs.kuleuven.be/~dirk.craeynest/ada-belgium/ev...). There are more articles on the internet on Ada Ravenscar tasking profile and full Ada tasking.

Recently AdaCore announced they are adding support for CUDA applications in SPARK (https://developer.nvidia.com/gtc/2020/video/s21122-vid)

Re:Rust concurrency: the archetype of a message-passing bug by mratsim on Thursday June 25, 2020 @05:19AM (#23638571)
Ah yes, I watched that talk at FOSDEM 2019, it was very nice.