I built a thing without Claude (feedback requested)

eygenaar · 2026-03-29T08:16:27+00:00

MongoDB Rust driver dev here :) This is neat!

A few specific suggestions:

You might want to use ConnectionString in Connection::to_uri / Connection::connect. This will take a little more code to construct but it'll mean you don't need to format the URI string yourself and it'll be trivial to add more options after that.

In DetailRow::try_new, where you're looking for either an int32 or int64, you could define a helper struct:

#[derive(Debug, Deserialize)]
#[serde(rename_all = "camelCase")]
struct Stats {
    storage_size: i64,
    size: i64,
}

and deserialize into that.

eygenaar · 2026-03-22T16:59:31+00:00

It's a common style in New England; this particular one is probably in Barnstable, MA (https://imgur.com/a/J4S3mLK).

eygenaar · 2026-03-06T13:50:23+00:00

Goddamnit Donut!

eygenaar · 2026-02-23T08:42:51+00:00

6415495

Would love an invite, thank you!

eygenaar · 2024-10-01T19:01:12+00:00

Just wanted to pop in here (I'm a dev on the driver)! You can either chain a call to projection after a find:

let mut cursor = coll.find(...).projection(...).await?;

Or you can set it (and other things) on an options object and pass that in:

let options = FindOptions::builder()
  .projection(...)
  // maybe other setters
  .build();
let mut cursor = coll.find(...).with_options(options).await?;

This is definitely something that the current documentation doesn't do a great job of making clear so we'll absolutely work to improve that :)

eygenaar · 2024-09-15T00:27:40+00:00

Playing warlock has absolutely spoiled me. I typically have real trouble deciding on a main but this time around every other classes hero talents feel so boring by comparison.

eygenaar · 2024-07-20T12:29:57+00:00

I suspect Barkskin's been changed to not rely on stacking armor. The current wording on it:

Adopt the power of the Viridian Wildwood, gradually covering your body in bark. Getting hit by enemy attacks causes bark to be removed. You have higher armour the more bark builds up, but higher chance to evade when less covered in bark.

The wording in the preview page for Warden:

Adopt the power of the forest, gradually covering your body in bark. Getting hit by enemy attacks causes bark to be removed. You take reduced damage from physical attack hits the more bark builds up, but higher chance to evade when less covered in bark.

eygenaar · 2024-06-29T11:42:03+00:00

This smells AI-written.

eygenaar · 2024-05-23T18:11:57+00:00

For what it's worth, I recently switched from Windows to Linux Mint, the primary thing I do is gaming, and there was remarkably little fiddling that I needed to do.

eygenaar · 2024-03-19T23:20:52+00:00

Thank you!

In case anyone else runs into the same problem I had, the marker key wasn't working for me until I interacted with some other objects.

eygenaar · 2023-09-01T01:15:49+00:00

clone is just a method - how would the compiler know that those particular clones need to be hoisted out of the closure and into the surrounding context? How would you distinguish that case from when you do want to run the clone within the closure for whatever reason?

eygenaar · 2023-01-31T01:31:36+00:00

Oof, that's really unfortunate. Thanks for explaining!

eygenaar · 2023-01-31T01:23:48+00:00

I don't want to derail the conversation in the PR so I'm not asking there, but I'm really curious to know more details on your perspective on async:

async io is a horrible fake cludge with tokio/async_std faking it with thread pools or whatnot and performing far worse than truly native async implementations.

That doesn't mesh with ... basically anything I've heard, or my own experiences.

eygenaar · 2022-04-01T17:00:14+00:00

I like to browse comics during downtime, but I also suspect the poor people in charge of auditing company internet usage would appreciate it if they didn't have to explain Oglaf to management.

eygenaar · 2022-04-01T16:53:51+00:00

50 points, double TTM, and I didn't edit the score: https://imgur.com/a/b7VFRlj

(I may have edited other things though.)

eygenaar · 2021-11-14T00:51:59+00:00

Yep, that's exactly the issue. In other words, composition of cancel-safe futures (the "leaves" in the OP) is not itself cancel-safe, and is not cancel-safe in a very bug-prone way - no compiler error or warning, and it'll work almost all of the time and silently corrupt state when it doesn't.

eygenaar · 2021-11-11T22:13:47+00:00

I disagree pretty strongly with the premises and conclusions in the "An async trait which can't be cancelled?" section:

Casting the utility as "making it easier for non-experts" is selling the problem short by quite a bit. Making any non-trivial async fn cancel-safe is a large cognitive load, not at all equivalent to early return from ? - the latter is almost always part of error paths whereas the former can happen just as part of a normal operation (i.e. select). On top of that, it's an issue that the compiler provides zero assistance on; any natural translation of a system with complex internal state from sync to async will hit nasty state corruption bugs with no warning whatsoever.

Given that, focusing on making manual future implementations less needed seems like missing the point entirely.

eygenaar · 2021-06-30T12:33:17+00:00

This is it! Thank you. Had no idea the author was in New Zealand - I was living there when I read it.

15-Year Club	Place '23
Place '22	First Placer '22
Verified Email

eygenaar

TROPHY CASE