David Wong
David Wong
Also this part needs to be removed (step 2 of section 5): > Note that the attacker can only violate correctness for nodes that do not re-execute transactions. Honest validators...
oh right, makes sense! thanks
I like it. I like that Rust also gives you a link that you can directly click on to get more information.
or `ocamlfind ppx_tools/dumpast -e "1 + 1"` (from https://tarides.com/blog/2019-05-09-an-introduction-to-ocaml-ppx-ecosystem) > Similarly, you can use the -t or -p options to respectively pretty print ASTs from type expressions or patterns.
(https://ocaml-ppx.github.io/ppxlib/ppxlib/manual.html#what-is-ppx)
started here: https://github.com/o1-labs/ocamlbyexample/commit/7c6a95ddc67b6dd827172e87c735a95ed97f53dc
confirmed here https://stackoverflow.com/questions/71453556/should-i-use-bytes-or-string-in-ocaml?noredirect=1#comment126295401_71453556
the other syntax is also useful, as noted by the [manual](https://v2.ocaml.org/manual/locallyabstract.html) it allows functions to be generic: ```ocaml let rec f : type t1 t2. t1 * t2 list ->...
I guess that doesn't work for functions like `Fn.id` or acting on containers. For example: ```ocaml let concat (l1 : 'a list) (l2 : 'a list) : 'a list =...
Would you be up for a PR :)?