News for hackers. Stuff that matters.

A comment on Making Rust a Better Fit for Cheri and Other Platforms. Parent comment

Re:Making Rust a Better Fit for Cheri and Other Platforms by saagarjha on Thursday April 14, 2022 @10:26AM (#31027478)
> Capabilities should not be visible to users of the Rust language what-so-ever and should only exist in the compiler, and nowhere else.

One important use of Rust is operating systems, allocators, and JIT compilers where security is important and interacting with capabilities is expected. You’ll really want some way to represent them in the language for these usecases.

[ Parent | on HN ]
Re:Making Rust a Better Fit for Cheri and Other Platforms by gpm on Thursday April 14, 2022 @10:45AM (#31027688)
Naively I think you can probably just expose interactions with them inside existing apis like "slice::split_at_mut", since the rust abstract machine already has the concept of pointers being able to access regions of memory.

You would probably have direct access to the primitives available, but discourage using them, because using them means non portable code.

[ Parent | on HN ]
Re:Making Rust a Better Fit for Cheri and Other Platforms by saagarjha on Friday April 15, 2022 @08:23AM (#31039375)
Right, the instances I'm mentioning are going to be parts of the codebase that are intended to be platform-specific.
[ Parent | on HN ]