Commitment printing bug
arthurpaulino opened this issue · 0 comments
arthurpaulino commented
Although opening a commitment works fine, printing seems to always indicate opaque data:
user> (commit '(13 . 21))
[2 iterations] => <Opaque Comm 0x178217493faea2931df4e333837ba9312d0bb9f59bb787c1f40fd3af6d845001>
user> (open 0x178217493faea2931df4e333837ba9312d0bb9f59bb787c1f40fd3af6d845001)
[2 iterations] => (13 . 21)