crates.io | The Rust package registry | DevOps library

Hey, I am working on putting up a rocket rest api with a mongodb database.

I have been able to create a successful connection to the MongoDB Atlas and put the resulting client into the state management of rocket via the manage builder function like this:

I'm trying to get clokwerk to schedule an asynchronous function to run every X seconds.

The docs show this example:

I am trying to build a POST handler, that receives JSON data with rocket (version: 0.5.0-rc.1).

This is the code I wrote:

I am working in an environment where I cannot use heap memory but only stack memory. To not be constrained by the #[no_std] enviroment I tried to use stack memory as heap memory with the linked-list-allocator crate. This was my approach.

I have some utility functions in tests/utils/mod.rs that are used by my integration tests, but I also want to create a testing binary that isn't run as part of cargo test but can use the functions in tests/utils/mod.rs. It's a utility that is useful for manual testing, but it only makes sense to run it manually; not using libtest.

The only solution I can think of is to put tests/utils/mod.rs in its own crate, but I'd really like to avoid that because publishing multi-crate workspaces to crates.io is a real pain. Another option would be to just move tests/utils/mod.rs to src/test_utils/mod.rs but that is a bit gross.

Is there a better solution? Maybe something using harness somehow?

Suppose we have two std::collections::HashMap-s, say HashMap and HashMap, and a function Fn(V1, V2) -> R.

How do I perform an inner join on these hashmaps so that I get HashMap on their shared keys as a result? Here's a reference implementation to illustrate what I mean:

I'm using the sqlx crate to interact with a Postgres instance.

I have the following function:

I'm currently trying to learn Rust (for embedded specifically), coming from a background of C for embedded systems and Python. So far, I've been reading Rust Programming Language and Rust for Embedded, and read a few blog posts on the web.

I want my first project to be a simple "Blinky", where an LED blinks infinitely. I've got an STM32L152CDISCOVERY board with an STM32L152 chip in it (basically same as STM32L151), which is a Cortex M3.

Instead of implementing everything from scratch, I want to leverage existing crates and HALs. I've found two that seem promising: stm32l1 and stm32l1xx-hal. I've tried to read the documentation of each of them and also part of the source code, but I still can't figure out how to use them correctly.

Got a few questions about Rust and about the crates:

1. I see that stm32l1xx-hal has a dependency on stm32l1. Do I need to add both as a dependency in my Cargo.toml file? Or will that create problems related to ownership?

2. Is this the correct way to add them? Why is the second one added like that [dependencies.stm32l1]?

   ...

I added this to my cargo toml file, following the instructions here