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

crates/monty/Cargo.toml

@@ -42,6 +42,12 @@ speedate = "0.17.0"
 itertools = "0.14.0"
 jiter = { version = "0.15.0", features = ["num-bigint"] }
 monty-macros = { workspace = true }
+# Portable monotonic clock: a drop-in for `std::time::Instant` that re-exports
+# std unchanged on native and WASI, and is backed by `performance.now()` on
+# `wasm32-unknown-unknown` (where `std::time::Instant::now()` panics). Keeps the
+# `max_duration` resource limit usable when `monty` is embedded directly in a
+# browser wasm module rather than run over WASI.
+web-time = "1.1"
 
 [features]
 # ref-count-return changes behavior to return information on reference counts to check they're correct

crates/monty/src/resource.rs

@@ -1,9 +1,12 @@
-use std::{
-    cell::Cell,
-    error::Error,
-    fmt,
-    time::{Duration, Instant},
-};
+use std::{cell::Cell, error::Error, fmt, time::Duration};
+
+// `web_time::Instant` is `std::time::Instant` on native and WASI targets, and a
+// `performance.now()`-backed clock on `wasm32-unknown-unknown`, where the std
+// `Instant::now()` panics ("time not implemented on this platform"). This keeps
+// the `max_duration` time limit working when `monty` is embedded directly in a
+// browser wasm module. Time behavior on all currently-supported targets is
+// unchanged (it re-exports std verbatim there).
+use web_time::Instant;
 
 use crate::{
     ExcType, MontyException,