livingcoder

I'm surprised this doesn't already exist.

After many years of using SO, I've started using ChatGPT for all of my programming questions and have not looked back once. For my usual "I know X is possible, but how do I do that in Y language" questions, it's been a dream using ChatGPT.

In Rust, using the Option and Result types make the general flow of the application much easier to organize, make modular, and reuse.

This was a good blog post. I particularly appreciated the statement about the validate and parse function comparison: "Both of these functions check the same thing, but parseNonEmpty gives the caller access to the information it learned, while validateNonEmpty just throws it away."

Is that a water dispenser? I need something like that.

They apologize in situations when it's not even a big deal, like walking past someone in the grocery store aisle who's trying to look at the items on the shelf.

I would love to see professional chess players give this a fair chance. The clock could stop when they declare their move verbally (ensuring that the game doesn't devolve into an endurance test) and start up again for the next player upon the move being completed.

Boo, just missed it.

Is this already in a crate? I'd be happy to change over from rusqlite to limbo, at least for the async functionality.

That's something I haven't heard before about the memory safety. In what ways is it not memory-safe?

At first I was disappointed to see this, but after looking into it it looks like they weren't using hyper as a means to migrate the project to Rust. If they're not going to move away from C, it seems like a fair decision.

There is a market for a game engine that uses algebraic variables and geometry to guarantee purely accurate collision detection. That said, a bit of searching shows that it's going to be much slower then current approximate approaches.