skapata has quit [Remote host closed the connection]
Tuplanolla has joined #racket
svm has joined #racket
nm0i_ has joined #racket
jA_cOp_ has joined #racket
Oxyd_ has joined #racket
Tuplanolla has quit [*.net *.split]
runrin has quit [*.net *.split]
nm0i has quit [*.net *.split]
mdhughes_ has quit [*.net *.split]
jboy has quit [*.net *.split]
jA_cOp has quit [*.net *.split]
msv has quit [*.net *.split]
Oxyd has quit [*.net *.split]
nm0i_ is now known as nm0i
runrin has joined #racket
msiism has joined #racket
jboy has joined #racket
Tuplanolla has joined #racket
mdhughes has joined #racket
<msiism>
bremner: command-line might help, yes. The problem (for me) is that it doesn't do POSIX-compliant parsing.
<bremner>
Is that like getopt?
<msiism>
Should be, yes. I never use getopt, though. Same goes for getopts.
<msiism>
A while ago, I tried to demontstrate what I beleive would be a way to have POSIX-compliant command-line parsing in Racket: https://git.sr.ht/~msi/rpack
<msiism>
I just went by what the standard says and tried to translate that into code.
<msiism>
I should probably brush that up a bit, though.
igemnace has quit [Remote host closed the connection]
igemnace has joined #racket
kratacoa has joined #racket
msiism has joined #racket
Origin has joined #racket
svm is now known as msv
kratacoa has quit [Ping timeout: 258 seconds]
msiism has left #racket [Konversation vaporized.]
kratacoa has joined #racket
skapata has joined #racket
msiism has joined #racket
mdhughes has quit [Read error: Connection reset by peer]
mdhughes has joined #racket
Everything has joined #racket
<Everything>
Hi all. I want to learn streams. But in racket, when I call (stream-from 10), I get only '#<stream>', but I wanted to see all the internals, including delay and force. Other Scheme implementations can show me stream's internals?
leungbk has joined #racket
kratacoa has quit [Ping timeout: 256 seconds]
<bremner>
Everything: one possible option is to use your own implementation of streams, but procedures are opaque in racket afaik, so most obvious implementation strategies will not easily show internals.