Closed ctm closed 1 year ago
This is due to wasm being 32-bit (hence the wasm32-unknown-unknown
target) and that causing problems with typenum.
For now I've just added a patch section to the top-level Cargo.toml:
[typenum-spike]% git diff Cargo.toml diff --git a/Cargo.toml b/Cargo.toml index 47959995..cdf68065 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -27,6 +27,9 @@ resolver = "2" [workspace.package] edition = "2021"
+[patch.crates-io] +typenum = { git = "https://github.com/benluelo/typenum", branch = "ben/192-const-generic-32-bit" } + [workspace.dependencies] simple_logger = { version = "4.2", default-features = false } chrono-tz = "0.8"
Figure out why building using generic-array 1.0.0 fails.
FWIW, I did the legwork for this before creating an issue because it was one of those things where if I couldn't quickly find a solution, one would probably show up in a day or two as others get bitten. Turns out, there was indeed already a solution.