Snapshot and Iterate class instances

[DrSensor]

• [ ] @iterate.for and @iterate.for(Class/module-path) decorator
• [ ] iterate.for(Class/module-path, async (index, {...accessors}) => {}, [max,min]?)
  • [x] forward iteration
  • [ ] backward iteration
  • [ ] forward/backward iteration with specific range
• [ ] iterate.current.index and iterate.current.length
• [x] iterate.skip, iterate.skip(index), iterate.skip(...accessors) to skip render upate
• [x] iterate.stop to stop iteration
• [ ] await iterate.resume and iterate.resume() which similar to yield and .next()
• [ ] snapshot(Class/module-path) return copy of databank accessor

Warning function generator might not fast enough so I'm using await iterate.resume instead of yield (need a benchmark to prove this)

Most likely await-ing is not optimal since it require async keyword. This make iterate() switch into concurrent iteration logic if it use async function although await iterate.resume doesn't need to be queued into microtask. 💡 Alternative: iterate.yield and iterate.resume()

Note await iterate.continue will render update the current changes from start/continued index to awaited index

Note snapshot and iterate for WASM only support module-path instead of module instance since it still unknown how import ? from "module.wasm" assert {type:"wasm"} will be executed

📚 References:

• WebAssembly/ES Module Integration (use instantiateStreaming)
• get all the declared imports of module.wasm (use compileStreaming)

[DrSensor]

Shortcut to create a new Controller for specific iteration

const ctl = new iterate
  .for(Counter, (index, {count}) => { ... })

The controller is persisted and you need to explicitly ctl.run() the iteration as many times as you want.