Tim Hutt
Tim Hutt
Oh you missed a `paddr` though...
Nice work everyone!
Yeah that seems reasonable.
The impact will be that *if* they want to support this optional format they need to install the json5 package (or whichever format we use). I don't understand how that...
> What npm supports, every tool effectively must support. This alternative format is **optional**. Third party tools can decide if they want to support it (potentially losing users) and users...
> without the effort and spec noise of pasting in prose-spec versions into the Sail spec - instead, given tags in the Sail spec, one can first automatically record off-line...
In what sense? My proposal would give you a way of actually answering questions like "have you tested everything in the spec?" and "is the model up-to-date with this version...
I think for *parsing* the logs you really want structured output. Parsing human-readable trace formats is generally a terrible idea, but it's difficult to get people to stop if there...
I just noticed there's [a new RVVI Text format in progress](https://github.com/riscv-verification/RVVI/blob/master/RVVI-TEXT/README.md). It actually looks pretty well thought out, and more efficient than JSON. I'll try adding support for that.
Hmm maybe I can just implement `serde::Deserialise` for `Value`? I will try... > they'll define a data type Server and a function server which is exposed as a Rust function...