Repository navigation
Internal Verus names and attributes generated by Verus macro are visible to Rust code #3149
Chris-Hawblitzel
started this conversation in
General
Replies: 3 comments 1 reply
|
This discussion was split off from issue #3147 and then edited . |
0 replies
|
As another example, Rust code can include |
0 replies
|
We don't want Rust code to access what we consider internal Verus state. Discussion question: should we treat outside access to Verus internals to be:
Also, how much does this matter: is this a high or low priority? |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
When Verus erases ghost code, a ghost function keeps its name and gets a body that panics, and so does the verified copy
_VERUS_VERIFIED_fof a function declared with#[verus_spec(with ...)]. Nothing checks that compiled exec code does not use these stubs.Other variants
#[verus_spec(with)] fn start() { .. }and a verifiedfn main() { _VERUS_VERIFIED_start(); }: the binary panics withnot implemented. The same withuse self::_VERUS_VERIFIED_start as main;, and with#[verifier::exec] proof fn main().All reactions