Our great sponsors
-
sqlx
🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite. (by launchbadge)
If I can give a recommendation, use sqlx for databases.
-
see here https://github.com/spacejam/sled#interaction-with-async
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Overview: I'm trying to write a simple REST API that lets you add or read messages from a HashMap on the server. To use this HashMap with Rocket I need to let Rocket manage its state. The compiler is demanding an implementation of a FromRequest trait on the state when it shouldn't be. (Notably, the implementation I'm borrowing from on GitHub doesn't have one at all).
-
Taking a quick look at state.rs, it looks like FromRequest is implemented for &State, not State. Small difference, but can you see if fn deposit_message(mail: Json, state: &State) compiles?
-
I'm currently looking into Amethyst and its pong tutorial. Amethyst looks like it'd be great for what it was designed for, but using it sort of feels like using a shotgun as a fly-swatter in my case.
-
If you're looking at Amethyst, you may want to consider bevy instead. I don't find a full ECS engine to be overkill at all. Even for basic games, the abstractions of an ECS can help make code structure decisions much simpler. In addition, learning an ECS would help to produce later games that benefit strongly from an ECS. In fact, regardless of the fact that you mentioned amethyst, I'd still recommend bevy.
-
I just published my awint system of crates today. I have a no_alloc_test crate in the repository that builds and links the main crate to make sure that no dependency on an allocator is brought in (building the main crate is not enough, it seems that the checks for an allocator only occurs when linking to a building binary). When I follow the exact sequence of instructions that the `no_alloc_build` job in the `.github/workflow` file takes, it works first time on a local machine (specifically, Debian WSL 2 with a freshly downloaded rustup), but it fails with linking errors on the Actions CI run. How do I debug this issue?
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
