2024/05/06

Newest at the top

2024-05-06 19:47:32 +0200justsomeguy(~justsomeg@user/justsomeguy) (Read error: Connection reset by peer)
2024-05-06 19:47:32 +0200wootehfoot(~wootehfoo@user/wootehfoot)
2024-05-06 19:45:07 +0200justsomeguy(~justsomeg@user/justsomeguy)
2024-05-06 19:42:13 +0200cheater(~Username@user/cheater) (Quit: Going offline, see ya! (www.adiirc.com))
2024-05-06 19:38:02 +0200justsomeguy(~justsomeg@user/justsomeguy) (Read error: Connection reset by peer)
2024-05-06 19:38:02 +0200euphores(~SASL_euph@user/euphores)
2024-05-06 19:34:33 +0200justsomeguy(~justsomeg@user/justsomeguy)
2024-05-06 19:32:12 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com)
2024-05-06 19:31:56 +0200target_i(~target_i@user/target-i/x-6023099)
2024-05-06 19:28:42 +0200justsomeguy(~justsomeg@user/justsomeguy) (Read error: Connection reset by peer)
2024-05-06 19:28:42 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2024-05-06 19:26:20 +0200justsomeguy(~justsomeg@user/justsomeguy)
2024-05-06 19:19:45 +0200euphores(~SASL_euph@user/euphores) (Quit: Leaving.)
2024-05-06 19:19:23 +0200justsomeguy(~justsomeg@user/justsomeguy) (Read error: Connection reset by peer)
2024-05-06 19:19:23 +0200destituion(~destituio@2a02:2121:2c4:e7b9:2895:2152:25e1:7ece) (Ping timeout: 268 seconds)
2024-05-06 19:17:48 +0200justsomeguy(~justsomeg@user/justsomeguy)
2024-05-06 19:12:57 +0200 <davean> yes you can but its almost always just wrong.
2024-05-06 19:12:12 +0200justsomeguy(~justsomeg@user/justsomeguy) (Read error: Connection reset by peer)
2024-05-06 19:12:12 +0200causal(~eric@50.35.88.207)
2024-05-06 19:11:34 +0200justsomeguy(~justsomeg@user/justsomeguy)
2024-05-06 19:05:31 +0200justsomeguy(~justsomeg@user/justsomeguy) (Read error: Connection reset by peer)
2024-05-06 19:05:31 +0200 <erty> Thanks for providing context. I was just curious whether it was possible to simply add a delay, without having to change the types of the parent function. 😅
2024-05-06 19:04:21 +0200justsomeguy(~justsomeg@user/justsomeguy)
2024-05-06 18:59:59 +0200raym(~ray@user/raym)
2024-05-06 18:58:47 +0200justsomeguy(~justsomeg@user/justsomeguy) (Read error: Connection reset by peer)
2024-05-06 18:58:47 +0200raym(~ray@user/raym) (Ping timeout: 264 seconds)
2024-05-06 18:58:05 +0200justsomeguy(~justsomeg@user/justsomeguy)
2024-05-06 18:57:29 +0200tri(~tri@ool-18bbef1a.static.optonline.net) (Ping timeout: 268 seconds)
2024-05-06 18:52:35 +0200tri(~tri@ool-18bbef1a.static.optonline.net)
2024-05-06 18:46:12 +0200justsomeguy(~justsomeg@user/justsomeguy) (Ping timeout: 255 seconds)
2024-05-06 18:46:08 +0200chele(~chele@user/chele) (Remote host closed the connection)
2024-05-06 18:44:31 +0200econo_(uid147250@id-147250.tinside.irccloud.com)
2024-05-06 18:36:29 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2024-05-06 18:32:56 +0200 <gastus> https://hackage.haskell.org/package/base-4.19.1.0/docs/Control-Concurrent.html#v:threadDelay @ erty Read the docs: There it says will not be scheduled earlier but will wait at least. So threadDelay will allow other theads to continue. So RTFM :-)
2024-05-06 18:32:49 +0200 <EvanR> more like no write
2024-05-06 18:32:20 +0200 <EvanR> what xD
2024-05-06 18:32:09 +0200 <EvanR> copy on write??
2024-05-06 18:31:18 +0200 <gastus> If you want to sleep until you release try reading from socket file or so and echo a byte into it to release the stalling.
2024-05-06 18:30:51 +0200kimiamania(~76637481@user/kimiamania)
2024-05-06 18:30:29 +0200kimiamania(~76637481@user/kimiamania) (Quit: Ping timeout (120 seconds))
2024-05-06 18:30:16 +0200 <gastus> If its testing only any of the solutions probaly get the job done. If you want to do A/B testing on web server which should not stall .. then you want ot use a version provide dby the GHC runtime which allows other threads to conitnue. So evenutally spawn 100 threads and see what happens with what sleep solution ? Then you know.
2024-05-06 18:29:24 +0200 <gastus> You can run a GHC complied program with different multithreading options. So looks like you're eventually touching that stuff.
2024-05-06 18:29:22 +0200 <erty> gastus: Thanks a lot. I will look into that.
2024-05-06 18:28:28 +0200 <gastus> https://hoogle.haskell.org/?q=sleep&hoogle=sleep And Hoogle says there are sleep implementations, too. Now you might perefer eg the GHC verison so that GHC can use CPU for other threads.
2024-05-06 18:27:48 +0200 <gastus> Most languages call it sleep, but https://stackoverflow.com/questions/47816174/how-to-sleep-or-delay-the-thread-in-haskell indicates threadDelay works
2024-05-06 18:27:33 +0200 <davean> It won't compile, for the obvious reason
2024-05-06 18:27:22 +0200 <gastus> Why not just try it ?
2024-05-06 18:27:18 +0200 <davean> gastus: it isn't about IO implimentations, its about how libraries interface with them
2024-05-06 18:26:37 +0200 <erty> davean: I just want to delay the execution by some time period
2024-05-06 18:26:33 +0200 <gastus> davean: I am not up to date about how many IO implementations exist today. In the past I heard about a rewrite with different locking features.