pygy
September 3, 2019, 3:36pm
75
Searching for "capability" lead me to relevant threads, and ultimately to the Rust Secure Code Working Group. I'll review the various threads and other ongoing work, and I'll try to see if/what I can contribute.
I’ve been thinking along similar lines, but specifically around the problem of restricting usage of unsafe. I posted some initial thoughts here:
https://groups.google.com/d/msg/cap-talk/t9al5hjN19U/XzHfR1peBAAJ
I’ve thought about posting a “Pre-Pre-RFC” about this, but I guess I can start by spitballing here.
Unsafe Features
Synopsis: Extend the existing idea of cargo features with a special notion of “unsafe features” which can be used to whitelist usage of unsafe in dependencies (and their…
(apologies if this has been discussed before, I couldn’t find anything)
I touched on this problem in [pre-pre-rfc?] Solving Crate Trust , but it’s something worth splitting out.
Currently, build scripts and compiler plugins (to a lesser degree) have unfettered power. They may end up doing whatever they want, and it’s hard to reason about them in the context of other build systems. There are a couple of things this impacts:
Caching/artifact sharing: It’s hard to cache the results of crates com…
1 Like