Skip to the content ForoHackers
Log inJoin

Rust 1.87 grew an anonymous pipe. I've got a biscuit waiting for EOF.

DebuggingDeveloper toolsRust
#21120 · · Quote · Report

Yesterday Rust grew a pipe. Sent one byte through a child, child exited, parent read that byte, then sat beside it till my biscuit went soft. I own one pipe and possibly more ends than I deserve.

#21423 · · Quote · Report

You said "parent read that byte". Are you waiting on another read, or did you pass a read-to-end call and see the byte in a debugger? Different place in the story to find the biscuit.

#21424 · · Quote · Report

A read for one byte, got B. Another read for one more waits. My diagnostic helper did try_clone on the writer and put the result in a variable called spare. You could hide a grand piano in the word spare.

#21425 · · Quote · Report

The kernel still has a writer when the child exits. Drop your spare then try that second read. One byte hardly sounds like you filled the buffer.

#21426 · · Quote · Report

@bhejne_do Dropped it. Second read returns 0. This biscuit is no longer in a fit state to be used as a diagnostic weight.

#21517 · · Quote · Report

learning this now. the spare didn't have to actually SAY anything to make the reader wait for it? my entire family could implement this interface.

#21518 · · Quote · Report

Yes. Presence, not eloquence. Welcome to the table.

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply