Make iterate() lazily evaluated on wasm

[diegoreis42]

#514

Introduces a new feature for lazy evaluation in the Statement.raw().iterate() method and includes related changes in both the test and implementation files. The most important changes include adding a test case for lazy evaluation, creating a RowIterator struct, and modifying the iterate method to use this new struct.

Everything seems to works fine, but suggestions on code improvement and test use cases are welcoming.

[penberg]

@diegoreis42 Looks great! I am guessing some auto-formatted turned the diff on the test file into something that's pretty unreadable. Can you please change back to 4 space indent to make that change readable?

[Lemon-Peppermint]

@diegoreis42 FYI, js_sys::Array implements FromIterator, you could move your RowIterator.next() method to an implementation of Iterator then use that to construct your Array instead of going through an intermediate Object.

Edit: Never mind , just checked the Array::from_iter() implementation, it still eagerly evaluates the arguments.

[diegoreis42]

@diegoreis42 Looks great! I am guessing some auto-formatted turned the diff on the test file into something that's pretty unreadable. Can you please change back to 4 space indent to make that change readable?

Yeah sure, sorry about that.

[diegoreis42]

Hey, I thought that CI test suit would run wasm tests but, apparently, it doesn't. Some changes are needed to conform with previous tests, I'm working on this.

In order to test if the rows are lazily loaded, I wrote a SQL trigger, but it has not been implemented yet by Limbo, so it throws an error. Any inputs in how to test if the rows are lazily loaded?

Btw, perhaps it would be nice to include wasm testing on CI, afaik only wasm build is executed, I can try do this in another PR.

[diegoreis42]

@penberg in the iterator, when a row is busy it returns undefined, it's fine or other behavior is required?

[pereman2]

Can you rebase, it will be unreviewable if I cannot find the changes.

[diegoreis42]

Can you rebase, it will be unreviewable if I cannot find the changes.

Done.