It's not SQLite replacement if not no_std

[michalfita]

One of key features of original SQLite is that in can be built for bare metal system and used without OS in place on microcontrollers. To achieve the same, the core of Limbo would have to be no_std with ability to plug in a storage backend that's non-Linux thing. But I don't see #![no_std] clause in core's lib.rs.

Is this no-feature for Limbo being oriented for cloud solutions?

[penberg]

I actually don't mind supporting no_std! Just not something that has been on my radar. I/O is already pluggble so we're not dependent on Linux. If someone wants to work on this, would love to see it happen!

[michalfita]

The hard part: all your dependencies have to support no_std.

[penberg]

@michalfita Sure, but I would actually anyway prefer that. Let me convert this into an issue.

[Fansport1giris]

You’re correct that the absence of #![no_std] indicates that Limbo's core is not designed for no_std environments.

[Fansport1giris]

This aligns with its orientation towards cloud solutions where the underlying infrastructure typically assumes the presence of an operating system and standard libraries.

[Fansport1giris]

For bare-metal systems or microcontrollers, making the core no_std compatible would require significant design changes, including abstracting away dependencies on system-level APIs and providing configurable, lightweight storage backends suitable for non-Linux platforms.