2024/04/28

Newest at the top

2024-04-28 03:37:12 +0200philopsos(~caecilius@user/philopsos) (Ping timeout: 255 seconds)
2024-04-28 03:36:00 +0200causal(~eric@50.35.88.207)
2024-04-28 03:35:21 +0200waleee(~waleee@h-176-10-144-38.NA.cust.bahnhof.se) (Ping timeout: 272 seconds)
2024-04-28 03:33:07 +0200otto_s(~user@p5b0442ac.dip0.t-ipconnect.de)
2024-04-28 03:31:23 +0200otto_s(~user@p4ff27de0.dip0.t-ipconnect.de) (Ping timeout: 252 seconds)
2024-04-28 03:19:36 +0200euleritian(~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de) (Ping timeout: 268 seconds)
2024-04-28 03:12:09 +0200[Leary](~Leary]@user/Leary/x-0910699)
2024-04-28 03:09:09 +0200jdbres(~jdbres@user/jdbres)
2024-04-28 03:07:31 +0200sawilagar(~sawilagar@user/sawilagar) (Ping timeout: 255 seconds)
2024-04-28 03:01:56 +0200mechap(~mechap@user/mechap) (Quit: WeeChat 4.2.2)
2024-04-28 02:57:05 +0200y04nn(~username@2a03:1b20:8:f011::e10d) (Ping timeout: 268 seconds)
2024-04-28 02:54:22 +0200madeleine-sydney(~madeleine@c-76-155-235-153.hsd1.co.comcast.net)
2024-04-28 02:34:37 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Client Quit)
2024-04-28 02:34:04 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2024-04-28 02:34:03 +0200Tuplanolla(~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Quit: Leaving.)
2024-04-28 02:28:40 +0200xff0x(~xff0x@2405:6580:b080:900:a359:eeea:f982:7525) (Ping timeout: 245 seconds)
2024-04-28 02:22:00 +0200madeleine-sydney(~madeleine@c-76-155-235-153.hsd1.co.comcast.net) (Quit: Konversation terminated!)
2024-04-28 02:13:21 +0200euleritian(~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de)
2024-04-28 02:11:26 +0200 <dolio> EvanR: Right, exactly.
2024-04-28 02:11:12 +0200smogeb(~smogeb@2603:7000:4b42:1100:d8aa:e17a:f1f9:f7b4) (Quit: Client closed)
2024-04-28 02:10:50 +0200euleritian(~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de) (Ping timeout: 268 seconds)
2024-04-28 02:10:22 +0200zetef(~quassel@2a02:2f00:5202:1200:2128:605:71c4:66a4) (Remote host closed the connection)
2024-04-28 02:07:07 +0200 <smogeb> what's the best book to write a interpreter (that is not scheme) ??
2024-04-28 02:04:37 +0200 <EvanR> you could use IVar in the story. the value you get back from executing the unsafeInterleaveIO action could be an IVar behind the scenes. And some thread is responsible for doing the i/o and writing the IVar
2024-04-28 02:03:19 +0200machinedgod(~machinedg@d173-183-246-216.abhsia.telus.net)
2024-04-28 01:54:02 +0200smogeb(~smogeb@2603:7000:4b42:1100:d8aa:e17a:f1f9:f7b4)
2024-04-28 01:51:23 +0200smoge(~smoge@2603:7000:4b42:1100:d8aa:e17a:f1f9:f7b4) (Client Quit)
2024-04-28 01:50:50 +0200dispater-(~dispater@host-78-146-88-32.as13285.net) (Remote host closed the connection)
2024-04-28 01:50:07 +0200dispater-(~dispater@host-78-146-88-32.as13285.net)
2024-04-28 01:49:53 +0200smoge(~smoge@2603:7000:4b42:1100:d8aa:e17a:f1f9:f7b4)
2024-04-28 01:44:28 +0200hiredman(~hiredman@frontier1.downey.family) (Quit: Lost terminal)
2024-04-28 01:29:41 +0200madeleine-sydney(~madeleine@c-76-155-235-153.hsd1.co.comcast.net)
2024-04-28 01:25:26 +0200yin(~yin@user/zero) (Ping timeout: 256 seconds)
2024-04-28 01:23:14 +0200[Leary](~Leary]@user/Leary/x-0910699) (Ping timeout: 252 seconds)
2024-04-28 01:12:34 +0200philopsos(~caecilius@user/philopsos)
2024-04-28 01:10:04 +0200tri(~tri@ool-18bc2e74.dyn.optonline.net) (Ping timeout: 255 seconds)
2024-04-28 01:05:45 +0200reki(~halloy490@broadband-5-228-80-43.ip.moscow.rt.ru) (Remote host closed the connection)
2024-04-28 01:05:33 +0200tri(~tri@ool-18bc2e74.dyn.optonline.net)
2024-04-28 01:03:56 +0200reki(~halloy490@broadband-5-228-80-43.ip.moscow.rt.ru)
2024-04-28 00:59:08 +0200 <monochrom> Now v will be 5 or 6 or unchanged at unknown future times depending on when will x or y or neither is evaluated.
2024-04-28 00:57:57 +0200 <monochrom> Consider do { x <- unsafeInterleaveIO (writeIORef v 5 >> pure ()); y <- unsafeInterleaveIO (writeIORef v 6 >> pure ()) ; ... }
2024-04-28 00:57:43 +0200acidjnk(~acidjnk@p200300d6e714dc03d4ff90a1ba0ea518.dip0.t-ipconnect.de) (Ping timeout: 260 seconds)
2024-04-28 00:49:22 +0200stiell_(~stiell@gateway/tor-sasl/stiell)
2024-04-28 00:48:41 +0200stiell_(~stiell@gateway/tor-sasl/stiell) (Remote host closed the connection)
2024-04-28 00:45:16 +0200 <geekosaur> unprincipled coroutines
2024-04-28 00:42:12 +0200 <yin> got it
2024-04-28 00:41:47 +0200 <dolio> When you need something, your thread gets interrupted and the one that was supposed to calculate it runs instead.
2024-04-28 00:41:05 +0200 <dolio> You can think of it as concurrency where the scheduling gets informed by the lazy evaluation.
2024-04-28 00:38:48 +0200 <yin> is it just concurrent output or something else?
2024-04-28 00:38:41 +0200peterbecich(~Thunderbi@47.229.123.186) (Ping timeout: 252 seconds)