Open mstksg opened 6 months ago
Whoops I just noticed this is a duplicate of #3 (addressing #1) which was closed. Maybe there is something coming down the pipeline that will resolve this?
Whoops I just noticed this is a duplicate of #3 (addressing #1) which was closed. Maybe there is something coming down the pipeline that will resolve this?
It seems to be closed unintentionally, just by virtue of upstream branch being gone.
Unless I am misunderstanding the purpose of the test, it looks like the
crypton-x509
test suite requiresx509
instead ofcrypton-x509
, which, when compiling, fails because the appropriate Arbitrary instance is not defined. I am guessing this is not intentional because we define Arbitrary instances for the crypton-x509 types of the same name, but do not use them AFAICT. This seems to only be an issue forcrypton-x509
and not the others.