logoalt Hacker News

ameliusyesterday at 4:56 PM1 replyview on HN

This is a nice exercise for compiler researchers.

I suppose it can be done on various levels, with various performance trade-offs.


Replies

convolvatronyesterday at 5:45 PM

more specifically, one can introduce policies into the runtime, or given rust hoist at least some of them into compiletime that would do things like (a) enforce syscall filtering based on crate or even function (b) support private memory regions for crates or finer grained entities that are only unlocked upon traversing a declared call-gate (c) the converse, where crates can only access memory they themselves have allocated except a whitelist of parameters (d) use even heavier calling conventions that rpc to entirely separate processes