Safe code as an I/O requirement

Paulo Pinto via Digitalmars-d digitalmars-d at puremagic.com
Mon May 29 01:23:03 PDT 2017


On Sunday, 28 May 2017 at 16:58:53 UTC, aberba wrote:
> https://lwn.net/Articles/708196/
>
> From the look of things and feedbacks from several security 
> analysts and system developers, [exposed] I/O needs to be 
> memory safe.
>
> GStreamer multimedia library developed in C has safety issues 
> [see article]. What would its safety be if it was written in D 
> (along with its plugins)?

GStreamer has already adopted Rust and is slowly migrating away 
from C into Rust.

Search for their presentation at RustConf Kiev 2017.

Also GNOME guys have been having meetings with Rust design team 
as there is the possibility to replace Vala with Rust. See GUADEC 
Mexico city 2017.


More information about the Digitalmars-d mailing list