docs: locality names have Top_ prefix#20
Conversation
|
Hi! Thanks for checking out Owl :) We are currently working on a rewrite of the extraction mechanism. The current extraction mechanism produces unverified plain Rust implementations. When the rewrite is complete, extraction will generate formally verified Rust implementations that are proved to have the same input-output behavior as the Owl source program, using Verus, a deductive program verifier for Rust. The issue about locality naming has been fixed in that branch, but we didn’t backport it into the old Rust extraction mechanism. We hope to have a version of the new extraction mechanism merged soon. |
|
That's exciting news, @pratapsingh1729. I've assumed there are implementation changes forthcoming, but I at least needed to understand the delta between the documented and actual paths in order to try out the current implementation on |
The extraction I see from
docs/encrypted_key_basic.owlas of a4108a6 includes theTop_prefix both in the arguments expected bymain()and in the names of the configuration files generated bycargo run -- config.