Rendered at 10:50:39 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
jacobjwalters 46 minutes ago [-]
What is the program logic used here? The num_integer verification example seems to be hardcoding addresses in the spec; what if I want to reason about larger programs that dynamically allocate, where the addresses may not be known statically? How can I make sure these do not overlap? And since this is a shallow embedding into lean, what’s the approach for verifying properties of non-terminating programs?
himata4113 6 hours ago [-]
talos is already in use by https://github.com/siderolabs/talos, was confused for a second when I saw talos and wasm for a second, got excited about native wasm pod support.
I’m on the Cajal team - not OP, but happy to answer questions.
The core bet is that Wasm is a good verification target (close to compiled artifacts, many languages target it), and Lean is the right place to do verification.
Super interested in hearing from people working with Lean, compilers or other Wasm verification frameworks (eg Iris-Wasm).
kdavis 4 hours ago [-]
What other verification targets did you consider?
quietusmuris 18 hours ago [-]
Interesting. Do I have to write specs in Lean against the Wasm semantics or can you annotate Rust directly?
CurryFurry 2 hours ago [-]
For "Lean"? LeaRn? Lean Manufacturing? Stupid one-word techbro product names.
The core bet is that Wasm is a good verification target (close to compiled artifacts, many languages target it), and Lean is the right place to do verification.
Super interested in hearing from people working with Lean, compilers or other Wasm verification frameworks (eg Iris-Wasm).