Anthony Dodd

@somehowchris hey, that's a good idea. Will do.

Definitely, though in this case it wouldn't make any difference. The only reason I haven't already done so is due to time constraints, not because I was unaware of the...

@somehowchris as it turns out, we are blocked on upgrading to Tokio 1.0 until the underlying MongoDB crate updates. Wither is just a lightweight dependency on top of the `mongodb`...

@simoneromano96 I definitely need to get some other folks involved in keeping this project alive. I'll send you an invite!

> in production Woot woot! Becoming more and more common place these days, but kudos on staying intrepid! Wither does not currently offer any convenience mechanism for joins. Though doing...

I dig it. We will need to put a design together on what we would like to see for Wither aggregations. Glorified wrapper around `$lookup`, or something more sophisticated.

@wbrickner that's an excellent idea, and I think we've got a lot of potential there. We can generate pretty much any code we want to from the derive macro. I...

@No9 as of master today, yes. That is correct. Previously, there was a bit more logging within the index synchronization code; however, that has been removed recently due to some...

@No9 if you are up to the challenge, I think an excellent approach for this lib would be to use [`#[tracing::instrument(level="trace")]`](https://docs.rs/tracing/0.1.19/tracing/attr.instrument.html) on our Model trait. Any other async methods /...

👋 @wbrickner As of now, the answer is no. However, there is a short-term workaround, as well as a long-term solution. - short-term: you could do `Model::collection(&db).insert_many(...)`. [Docs for that...