tealsql VS crates.io

A project that uses tealr can be found at https://github.com/lenscas/tealsql/tree/master/pgteal, with online documentation available over at https://lenscas.github.io/tealsql/

There is also https://github.com/lenscas/tealsql which is used as kind of showcase project for tealr and tealr_doc_gen. While at the same time (hopefully) filling a pain point in the lua/teal eco system.

tealsql, my sql library for lua: Right now, it is being used to dog feed the changes in tealr. So, mostly improving its documentation, and preparing it to release it.

last weekend I put in some more time in tealsql, a postgresql client written in Rust for lua/teal.

The main focus is my sql client for teal/lua https://github.com/lenscas/tealsql , mainly getting rid of every part in the api that doesn't have a good type yet on the teal side of things (any, {any:any}, etc.

tealsql, an sql client for teal/lua. Current plan is to get the async api finished (right now it ignores every error but otherwise works without problems).

Rust has a rich ecosystem of frameworks and libraries that let you read, parse, and manipulate text files, interact with cloud services and databases, and perform any other job that your project's development workflow may require. And because of its strong typing and tight memory management, you are much less likely to write programs that behave unexpectedly in production.

All the code discussed in this article can be accessed through this repository. For integration with existing projects consider using keyword_extraction crate available on crates.io.

So, be sure to double-check your critical libraries and be sure their alternatives exist in the Rust ecosystem. There’s a good chance the crates you need are available in Rust's crates.io repository.

The previous section was very simple, this section is also very simple but introduces us to cargo which is Rust's package manager, as a JS dev my mind goes straight to NPM.

Now, there has to be a place where all these packages come from. Similar to npmjs registry, where all node packages are registered, stored and retrieved, Rust also has something called crates.io where many helpful packages and dependencies are registered.

Before proceeding, let's check https://crates.io/, the official Rust package registry.

The most thrilling aspect has been the joy of writing the backend. It's like every struct, enum, and method in Rust forms this interconnected Multiverse of code , which you can see in crates.io which is best Documentation experience I Ever Had.

5. Crates.io

When using crates from eg. crates.io, and also things like std and core

Vendoring your packages was very tedious to even remotely get to work with Cargo. I spent a very long time getting Cargo to work together with cargo-local-registry. We vendor crates from crates.io and a custom internal registry.