Alex Helfet

That blog post \[1\] is an excellent reference! It describes some of the problems in using mtimes and hashes in build systems and describes the approach used by the tool...

As far as I can tell, neither `emit` or `slog` seem to support arbitrary types as structured values (see [emit's Value enum](http://emit-rs.github.io/emit/emit/events/enum.Value.html), [slog's Serializer trait](https://docs.rs/slog/2.0.6/slog/trait.Serializer.html)). I found myself wanting to...

`Arc` already implements `Sync` automagically ([Mutex docs](https://doc.rust-lang.org/std/sync/struct.Mutex.html)) and `Connection` requires `Send`. So can you just wrap transactions in `Arc` in your app?

In case other people find this via Google and need a workaround, this is mine using [qsv](https://github.com/jqnatividad/qsv) and [jq](https://github.com/stedolan/jq): `< my.csv qsv tojsonl | jq '.RAW_JSON' -r` I would still...

I started a debug tooling [thread](https://users.rust-lang.org/t/arm-embedded-tooling-feature-discussion-on-itm-crate/14486/3) on users.rust-lang before finding this RFC. There I wrote: > On the microcontroller we probably want Rust support for: > > * TPIU configuration...

Optional dependencies and feature flags are very similar ([cargo docs on features](https://doc.rust-lang.org/cargo/reference/manifest.html#the-features-section)), so whichever is fine. If you have downstream dependencies that optionally use alloc/std, I think you may need...

> This is a well-known problem in the Rust ecosystem, and my opinion is that using lifetimes on long-lived objects is almost always "wrong" (in the sense that it leads...

> The current situation makes it impossible to make composable iterators over a query: -- https://github.com/rusqlite/rusqlite/issues/1337#issuecomment-1656702828 You can accept closure parameters to compose queries, just as [`Statement::query_map`](https://docs.rs/rusqlite/latest/rusqlite/struct.Statement.html#method.query_map) does.

@gwenn, I often find I can use `Pin` these days instead of reaching for a self-referencing `struct` crate (which are often weird and have their own subtle semantics, whereas many...

> The original issue is that you cannot have a `Store` **without** lifetime. I'm not sure what you mean. That's exactly what I have in my code. In one crate...