David Komer

> Would appreciate any suggestions I've been thinking about this a lot lately, diving into Workers (and loving it!) still not sure I have a strong enough grasp of the...

opened a PR to demonstrate: https://github.com/cloudflare/workers-rs/pull/530

From the peanut gallery (just sorta looking through some issues) I think this is more like the sort of thing that could/should be in optional community-driven wasm crates, rather than...

btw, to access properties on the global namespace, you don't really need direct access to globalThis, you can just create bindings via `js_namespace` property of wasm_bindgen. At the top level...

> All of that exists in the web_sys crate Can you show me an example? As far as I can tell, the web_sys crate expects plain objects and strings, there's...

note that you may also have to allow some headers, e.g. `.with_allowed_headers(["*"]);`

Yet another small adaptation. If there's something wrong with this, please let me know - but it seems to work perfectly to suspend only on the first load and then...

What I would expect, just looking at it from a contract dev perspective (not necessarily the inner workings of the storage): * An iterator that never calls Next() to be...

Yes, I am primarily focused on the Rust side and should have used lowercase `next()`. It would be very unexpected for there to be a cost for iterator creation itself....

Alternatively, separate it into an explicit method where `.iter()` is the free part. I like this better, no hidden costs, and more idiomatic: ```rust // expensive let my_storage_range = my_map.range(...);...