oh, oh wow
-
we disapprove of global mutable state, so whenever we do add a non-waiting variant, it would be a separate call with a separate name, not a flag we toggle
(at the kernel level, it's an
ioctl()that you do on the file descriptor, which persistently changes its behavior, but we can still organize our tooling to hide that fact, if we want, and we do)notionally it could have the same responsibilities but in a non-waiting version
or we could break the responsibilities down into even more granular pieces. hm hmmm. these are deep questions
-
(at the kernel level, it's an
ioctl()that you do on the file descriptor, which persistently changes its behavior, but we can still organize our tooling to hide that fact, if we want, and we do)notionally it could have the same responsibilities but in a non-waiting version
or we could break the responsibilities down into even more granular pieces. hm hmmm. these are deep questions
"peek" is already a really nice word for "look to see what's there but carefully don't change anything"
it's not immediately obvious what word we would use for "be even more careful than peeking, just make it really quick"
oh - "glimpse" lol... if we want to run with the visual metaphor. maybe we do.
-
"peek" is already a really nice word for "look to see what's there but carefully don't change anything"
it's not immediately obvious what word we would use for "be even more careful than peeking, just make it really quick"
oh - "glimpse" lol... if we want to run with the visual metaphor. maybe we do.
okay. fine. we aren't deciding on "glimpse" now, we just wanted to know there's at least one reasonable way forward before we proceed with "peek". there is, so we're going to proceed. yay
-
okay. fine. we aren't deciding on "glimpse" now, we just wanted to know there's at least one reasonable way forward before we proceed with "peek". there is, so we're going to proceed. yay
keeping these big-picture concerns in mind can be tedious
-
keeping these big-picture concerns in mind can be tedious
hmmmm okay, so, we think we'll have
consumedo nothing if the buffer is already empty -
hmmmm okay, so, we think we'll have
consumedo nothing if the buffer is already emptywe could make it silently corrupt internal data structures in that case, but that feels pointlessly cruel to our future selves
-
(at the kernel level, it's an
ioctl()that you do on the file descriptor, which persistently changes its behavior, but we can still organize our tooling to hide that fact, if we want, and we do)notionally it could have the same responsibilities but in a non-waiting version
or we could break the responsibilities down into even more granular pieces. hm hmmm. these are deep questions
@ireneista preadv2, pwritev2, send, recv, sendmsg, recvmsg, and the like all have ways to avoid blocking.
-
R relay@relay.infosec.exchange shared this topic
-
we could make it silently corrupt internal data structures in that case, but that feels pointlessly cruel to our future selves
@ireneista Isn’t the complete lack of type checking in Forth already cruel?
-
@ireneista Isn’t the complete lack of type checking in Forth already cruel?
@alwayscurious it's for sure a thing we're going to change
-
@alwayscurious it's for sure a thing we're going to change
@ireneista Static or dynamic?
