News for hackers. Stuff that matters.
Re:Towards Linux Kernel Memory Safety by jhasse on Thursday November 16, 2017 @08:02AM (#15712299)
Most things get moved to the heap.
Re:Towards Linux Kernel Memory Safety by pjmlp on Thursday November 16, 2017 @08:46AM (#15712542)
Only in GC languages that don't offer good language features for value types, which usually isn't the case with the ones targeted for low level systems development.
Re:Towards Linux Kernel Memory Safety by Rusky on Thursday November 16, 2017 @01:20PM (#15715078)
"Good language features for value types," while retaining memory safety, means at least one of these things:

* Boxing anything you take a reference directly to

* Forbidding sum types and complicating the GC to allow interior pointers

* Forbidding references to value types

* A borrow checker

Guess which one is most flexible, and novel in Rust.

Re:Towards Linux Kernel Memory Safety by pjmlp on Thursday November 16, 2017 @01:39PM (#15715266)
A language like Modula-3 doesn't suffer from those issues.

We only don't have it thanks to Compaq killing the project after acquiring DEC Olivetti. Politics as usual.

Rust ideas come from Cyclone and ATS, it is not novel in Rust.

The borrow checker still is pretty much WIP, that the NLL changes will surely improve, but don't not yet solve all ergonomic problems.

Re:Towards Linux Kernel Memory Safety by Rusky on Saturday November 18, 2017 @02:20AM (#15728129)
Modula-3 either uses one of those techniques, or is not memory safe. (Looks like primarily the first one- manual deallocation is unsafe and it relies on GC for the rest?)

Cyclone and ATS do not have Rust's combination of ownership and borrowing.