Markus Alexander Kuppe
Markus Alexander Kuppe
Like I said, the link could include a checksum over the spec, and error or warn if one loads an trace for a spec that does not match.
If there is interest and more Go code whose correctness should be validated, I'd be happy to explore the (low-level) program execution to (high-level) spec [trace checking technique](https://www.youtube.com/watch?t=1061&v=TP3SY0EUV2A&feature=youtu.be). It would...
> To be discussed: > > 1. All client requests are identical at the moment `[request -> 42, contentType |-> TypeEntry]`. > > Two ways to go here: > >...
For the record, I disagree with the removal of the formulas that are commented with TODO that need investigation. These are exactly the formulas that have to be added, thus,...
Specs are not code. On May 17, 2024 1:55:11 AM PDT, Amaury Chamayou ***@***.***> wrote: >@lemmy the project uses issues to track, discuss and prioritise work items. Please see the...
> it means that we can no longer call `RwTxExecuteAction` and `IsRoTxResponseAction` directly from the spec, and must replace them with copies that choose the txid instead. I don't understand...