Building the next generation of operating systems | TC39 Invited Expert Ex Tauri & CrabNebula Things I like: Open Source, Local First, Rust and All kinds of Music
Provenance „flows“ down from the allocator through your program right? (i do understand provenance can come from other sources too thats fine).
Being a provenance „source“ means calling from_exposed_provenance eventually picking up the „ambient provenance“ (right?)
Now here is my problem: I have both VirtualAddresses and PhysicalAddresses in my OS. Conceptually they live in different addresses spaces and carry their provenance. Essentially virtual addresses and physical addresses are orthogonal provenance hierarchies (right?) (much like separate virtual memory addresses spaces)
Is there a way to make this explicit in Rust? How do I explain switching addresses spaces to Rust under this model?
actually I was seriously considering doing a "program alignment chart" first
anyway, here's a version with pictures
Welcome to Elk!
Elk is a nimble Mastodon web client. You can login to your Mastodon account and use it to interact with the fediverse.
Expect some bugs and missing features here and there. Elk is Open Source and we're actively improving it as a community project. Join us and let's build it together!
If you'd like to report a bug, help us testing, give feedback, or contribute, reach out to us on GitHub and get involved.
(much like separate virtual memory addresses spaces)
