A Gopher Meets a Crab

joshka•about 3 hours ago

The weird-looking Rust isn’t really Rust being weird, it’s the type telling the truth.

   Result<Option<Result<Message, WsError>>, Elapsed>

That’s three independent “not the happy path” channels: timeout, stream closed, and websocket error.

The nicer version is not a cleverer match. It’s choosing a domain error shape and converting into it one layer at a time:

    let timed = tokio::time::timeout(duration, receiver.next()).await;
    let next = timed.map_err(|_| ReceiveError::Timeout)?;
    let item = next.ok_or(ReceiveError::Closed)?;
    let msg = item.map_err(ReceiveError::WebSocket)?;

The ugly line is what happens when you have not decided where to normalize the shape yet.

loeg•about 3 hours ago

  Result<(), ()>

Is pretty weird, though, no? Why would you want a unit value / error type?

RobotToaster•about 2 hours ago

Was anyone else expecting OpenClaw over gopher protocol?

saagarjha•about 1 hour ago

I feel like having an LLM write code in a language you aren't familiar with and then inspecting the results is kind of like hiring someone to speak Spanish for you and then being confused at the weird words they are using. Like, what would make you want to do this?

victorbjorklund•30 minutes ago

If you already speak French or another Romance language it isn’t a bad idea to just have a conversation in Spanish directly and then ask for clarifications anytime you don’t understand.

2ndorderthought•21 minutes ago

Which would be all the time? At which point you might be better served by learning from a source that has any guarantees of being correct and doesn't hallucinate. Like text books that have had several editions and are free on the Internet.

cpursley•about 1 hour ago

I’ve learned a ton of new things this way, even in a stack that I know really well. Ditto on all sorts of new little command line tricks that I was unaware of before.

wiseowise•38 minutes ago

Still better than deciphering C++ soup of characters.

cenamus•1 minute ago

std::expected and the utility functions for it (and_then(), or_else()) are pretty much the same, though? Or am I completely misunderstanding something?

nothinkjustai•about 2 hours ago

Um? Person vibe codes Rust. Output is stupid. The conclusion is either

a) Vibe coding produces bad code

b) Rust is weird

Somehow we’re supposed to accept b as the answer? Give me a break….

2ndorderthought•25 minutes ago

People really are forgetting how to think. While reading this blog post I almost immediately flipped into teaching confused freshmen taking the course that wasn't their major mode.

A Gopher Meets a Crab

⚡ Community Insights

Discussion (17 Comments)Read Original on HackerNews