[go: up one dir, main page]

SCORU: carbonate!

We need to check that the SCORU code is correctly carbonated, and fix it otherwise.

Meeting notes here.

Good entry-points for this are the SCORU operations (defined in Operation_repr) used in Apply, because every SCORU code is in the scope of applying at least one of these operations.

  • Benchmark when needed:
    • in snoop benchmarking closures, we should avoid definitions of the form let closure () = ignore p where p is of type _ Lwt.t because there is no strong guarantees about the actual execution of the promise (even though in practice this should work most of the time);
    • snoop does not take care of storage-related costs: hence a function that uses the storage can be benchmarked by snoop but we must manually add the cost of the storage accesses if there are not already taken care of by a carbonated storage.
  • Add regression traces that will show gas changes.

Sub-issues have been created to tackle each operation separately:

Edited by Nicolas Ayache