Bug: recursion in an `async fn` requires boxing

[svelterust]

Describe the bug

When trying to build surrealdb 1.5.0 -> 1.5.3 I get this issue with Rust:

error[E0733]: recursion in an `async fn` requires boxing
   --> /home/odd/.cargo/registry/src/index.crates.io-6f17d22bba15001f/surrealdb-core-2.0.0-1.5.1/src/idx/planner/iterators.rs:416:2
    |
416 | /     async fn next_batch<T: ThingCollector>(
417 | |         &mut self,
418 | |         tx: &Transaction,
419 | |         limit: u32,
420 | |         collector: &mut T,
421 | |     ) -> Result<usize, Error> {
    | |_____________________________^ recursive `async fn`
    |

Steps to reproduce

Add surrealdb crate with kv-mem, kv-rocksdb or kv-surrealkv.

Expected behaviour

It should build without any issues.

rippi/src-tauri via nix-shell-env ❯ cargo version
cargo 1.77.0-nightly (add15366e 2024-01-02)

[package]
name = "app"
version = "0.1.0"
default-run = "app"
edition = "2021"
rust-version = "1.60"

[build-dependencies]
tauri-build = { version = "1.5.1", features = [] }

[dependencies]
anyhow = "1.0"
serde_json = "1.0"
serde = { version = "1.0", features = ["derive"] }
tokio = { version = "1.38", features = ["full"] }
tauri = { version = "1.6.2", features = [] }
surrealdb = { version = "1.5.3", features = ["kv-mem"] }

[features]
# this feature is used for production builds or when `devPath` points to the filesystem and the built-in dev server is disabled.
# If you use cargo directly instead of tauri's cli you can use this feature flag to switch between tauri's `dev` and `build` modes.
# DO NOT REMOVE!!
custom-protocol = [ "tauri/custom-protocol" ]

SurrealDB version

surreal 1.5.3 on Linux for aarch64

Contact Details

[email protected]

Is there an existing issue for this?

• [X] I have searched the existing issues

Code of Conduct

• [X] I agree to follow this project's Code of Conduct