use web-time for the resource-tracker clock so max_duration works on wasm32-unknown-unknown

crates/monty/Cargo.toml

@@ -43,6 +43,13 @@ itertools = "0.14.0"
 jiter = { version = "0.15.0", features = ["num-bigint"] }
 monty-macros = { workspace = true }
 
+# `std::time::Instant` panics on `wasm32-unknown-unknown`, so the resource
+# tracker uses `web_time::Instant` (a `performance.now()`-backed drop-in) there
+# to keep `max_duration` working when `monty` is embedded directly in a browser
+# wasm module. Only that target needs it; every other target uses std directly.
+[target.'cfg(all(target_arch = "wasm32", target_os = "unknown"))'.dependencies]
+web-time = "1.1"
+
 [features]
 # ref-count-return changes behavior to return information on reference counts to check they're correct
 # should be used for testing only

crates/monty/src/resource.rs

@@ -1,9 +1,14 @@
-use std::{
-    cell::Cell,
-    error::Error,
-    fmt,
-    time::{Duration, Instant},
-};
+#[cfg(not(all(target_arch = "wasm32", target_os = "unknown")))]
+use std::time::Instant;
+use std::{cell::Cell, error::Error, fmt, time::Duration};
+
+// `std::time::Instant::now()` panics ("time not implemented on this platform")
+// on `wasm32-unknown-unknown`, so any `max_duration` limit aborts there. Swap in
+// `web_time::Instant` (a `performance.now()`-backed drop-in) only for that
+// target; every other target (native, WASI) keeps std, so the `web-time`
+// dependency is pulled in only where it's needed (see Cargo.toml).
+#[cfg(all(target_arch = "wasm32", target_os = "unknown"))]
+use web_time::Instant;
 
 use crate::{
     ExcType, MontyException,