When viewing a CBMC trace from RMC, a user might see something like this:
[main.assertion.1] line 28 assertion failed: std_string == \"1\": FAILURE
[main.assertion.2] line 30 assertion failed: weird_string == \"w\": SUCCESS
The top assertion is failing and the bottom is provably true, but both have assertion failed. I think this is just an artifact of how Rust proper prints assertions; it would be nice to remove this for CBMC usability.
When viewing a CBMC trace from RMC, a user might see something like this:
The top assertion is failing and the bottom is provably true, but both have
assertion failed. I think this is just an artifact of how Rust proper prints assertions; it would be nice to remove this for CBMC usability.