FStar
FStar copied to clipboard
A Proof-oriented Programming Language
Hello, when I run the following command,it occur some error, could you give me some suggests? $ opam pin add fstar --dev-repo [NOTE] Package fstar is already pinned to git://github.com/FStarLang/FStar...
Hi all -- is the following undesired behavior? ``` module Test type t = { x : nat; y : nat} // Parses correctly let tst (f : t ->...
I have noticed the following behavior with error messages: Construct an inductive type `t`, and have the constructors return `squash t` instead of `t`. (This is an easy thing to...
There doesn't seem to be a way to match on a negative integer. Here's a small reproduction: ``` module ExampleMatch let sign = (z:int{z = 0 \/ z = (-1)...
Recapping here the list of Steel work items **Code Refactoring** - [x] Replace SteelAtomic unobservable and SteelAtomic observable by SteelGhost and SteelAtomic - [ ] Remove the quantification on invariant_names...
https://github.com/FStarLang/FStar/blob/master/ulib/experimental/Steel.FractionalAnchoredPreorder.fst#L485
This may be related to the unfolding behavior of vprops. Could it be remedied by using strict_on_arguments? ``` module AVP open FStar.Ghost open Steel.FractionalPermission open Steel.Memory open Steel.Effect.Atomic open Steel.Effect...
When writing Steel specifications in selector style, the specifications themselves need to be framed. Consider this: First some general scaffolding for a test case, defining an abstract indexed vprop `p...
It seems that defining actions directly in an `effect` or `layered_effect` results in an error message. Below is an example which works: ```fstar module MWE let wpost a = a...
I ran across some behavior that’s surprising to me. The example below fails with the message `(Error 54) (*?u47*) _ is not equal to the expected type log': logT{Seq.Base.length log'...