Open OtaK opened 6 months ago
As an example, I made a fixed branch (based on tag v0.2.5) here: https://github.com/OtaK/formats/tree/otak/x509-cert-wasm
There's something else breaking inference here besides merely "WASM". We build all of our crates on WASM in CI:
https://github.com/RustCrypto/formats/blob/master/.github/workflows/x509-cert.yml#L33-L41
https://github.com/RustCrypto/formats/actions/runs/7602097002/job/20702246159
There is something else in your project, likely another crate which is breaking inference, although I'm not sure how.
The change on your PR looks fine but we literally just flipped over to the 0.3.0-pre release train days ago, which is very annoying.
I suppose we can backport it if need be.
I think you're right, it might be another crate disabling some features (like std
on the der
crate?) somewhere in my dependency tree. I'll run my patch for now and I have unfortunately no time to find another fix but I'll revisit later on and keep you updated.
Feel free to close the issue for now or keep it open if you'd like to keep track of this.
Your branch looks fine if you want to PR it. We should probably use something less ambiguous to prevent these sorts of inference errors
Hi! I'm currently running into these errors when targeting WASM (wasm32-unknown-unknown) with x509-cert:
I know the 0.3 release train is in full swing, but maybe we could sneak in a fix for this?
Cheers