Newest at the top
| 2025-11-19 12:04:24 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Ping timeout: 244 seconds) |
| 2025-11-19 11:59:50 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
| 2025-11-19 11:59:45 +0100 | <tomsmeding> | if you do mutations to the IORef also in unsafePerformIO, if I'm not mistaken it is prudent to add {-# OPTIONS -fno-cse -fno-full-laziness #-}, but this may be cargo-culting |
| 2025-11-19 11:59:41 +0100 | deptype | (~deptype@2406:b400:3a:9d2f:445f:7a99:cca5:e330) |
| 2025-11-19 11:59:24 +0100 | deptype | (~deptype@2406:b400:3a:9d2f:a8bf:8a15:2c9c:d5b2) (Remote host closed the connection) |
| 2025-11-19 11:59:09 +0100 | <tomsmeding> | probie: yes, if the only thing in unsafePerformIO is the creation of the IORef and the usages are in normal IO, that's fine |
| 2025-11-19 11:58:35 +0100 | CiaoSen | (~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen |
| 2025-11-19 11:47:14 +0100 | m1dnight | (~m1dnight@d8D861A17.access.telenet.be) m1dnight |
| 2025-11-19 11:45:15 +0100 | qqe | (~qqq@185.54.21.140) (Remote host closed the connection) |
| 2025-11-19 11:45:10 +0100 | ubert1 | (~Thunderbi@178.165.175.248.wireless.dyn.drei.com) ubert |
| 2025-11-19 11:44:17 +0100 | fp1 | fp |
| 2025-11-19 11:44:17 +0100 | fp | (~Thunderbi@wireless-86-50-140-28.open.aalto.fi) (Quit: fp) |
| 2025-11-19 11:44:10 +0100 | fp1 | (~Thunderbi@2001:708:150:10::7e06) fp |
| 2025-11-19 11:42:07 +0100 | m1dnight | (~m1dnight@d8D861A17.access.telenet.be) (Ping timeout: 240 seconds) |
| 2025-11-19 11:41:07 +0100 | <haskellbridge> | <Morj> I believe this is a common pattern in some situations, like for logging |
| 2025-11-19 11:39:42 +0100 | deptype | (~deptype@2406:b400:3a:9d2f:a8bf:8a15:2c9c:d5b2) |
| 2025-11-19 11:39:23 +0100 | deptype | (~deptype@2406:b400:3a:9d2f:a44b:c20f:51e9:62bc) (Remote host closed the connection) |
| 2025-11-19 11:35:47 +0100 | <probie> | can you get away with a top level IORef (with the NOINLINE unsafePerformIO shenangians)? |
| 2025-11-19 11:31:15 +0100 | trickard_ | (~trickard@cpe-62-98-47-163.wireline.com.au) |
| 2025-11-19 11:31:02 +0100 | trickard_ | (~trickard@cpe-62-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2025-11-19 11:29:33 +0100 | kuribas | (~user@ip-188-118-57-242.reverse.destiny.be) kuribas |
| 2025-11-19 11:19:31 +0100 | deptype | (~deptype@2406:b400:3a:9d2f:a44b:c20f:51e9:62bc) |
| 2025-11-19 11:19:17 +0100 | deptype | (~deptype@2406:b400:3a:9d2f:bc62:5450:375:9b3f) (Remote host closed the connection) |
| 2025-11-19 11:17:20 +0100 | trickard_ | (~trickard@cpe-62-98-47-163.wireline.com.au) |
| 2025-11-19 11:17:06 +0100 | trickard | (~trickard@cpe-62-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2025-11-19 11:14:32 +0100 | myxos | (~myxos@wsip-70-166-126-146.ph.ph.cox.net) myxokephale |
| 2025-11-19 11:10:45 +0100 | myxokephale | (~myxos@2001:579:8380:f20:a23e:fff0:9e97:fbf) (Ping timeout: 265 seconds) |
| 2025-11-19 11:10:06 +0100 | xff0x | (~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) (Ping timeout: 256 seconds) |
| 2025-11-19 11:06:00 +0100 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-11-19 10:58:04 +0100 | deptype | (~deptype@2406:b400:3a:9d2f:bc62:5450:375:9b3f) |
| 2025-11-19 10:57:45 +0100 | deptype | (~deptype@2406:b400:3a:9d2f:1ce0:1bdf:f2e5:d62b) (Remote host closed the connection) |
| 2025-11-19 10:54:40 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 264 seconds) |
| 2025-11-19 10:50:54 +0100 | __monty__ | (~toonn@user/toonn) toonn |
| 2025-11-19 10:50:29 +0100 | fp | (~Thunderbi@wireless-86-50-140-28.open.aalto.fi) fp |
| 2025-11-19 10:47:48 +0100 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-11-19 10:47:24 +0100 | fp | (~Thunderbi@wireless-86-50-140-28.open.aalto.fi) (Ping timeout: 252 seconds) |
| 2025-11-19 10:42:59 +0100 | fp | (~Thunderbi@wireless-86-50-140-28.open.aalto.fi) fp |
| 2025-11-19 10:41:39 +0100 | trickard_ | trickard |
| 2025-11-19 10:37:54 +0100 | deptype | (~deptype@2406:b400:3a:9d2f:1ce0:1bdf:f2e5:d62b) |
| 2025-11-19 10:37:40 +0100 | deptype | (~deptype@2406:b400:3a:9d2f:51eb:3f10:3160:250) (Remote host closed the connection) |
| 2025-11-19 10:36:37 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 264 seconds) |
| 2025-11-19 10:30:13 +0100 | <[exa]> | (Ideas/pointers very welcome. :) ) |
| 2025-11-19 10:29:58 +0100 | <[exa]> | WASM backend question: are there any good options for storing a "global state" in the WASM app? I see 2 possibilities, 1] serializing it out into wasm/js types, 2] having a hs/wasm function running permanently (thus holding the state), only communicating with the outside world via some kind of events (choice of "some" is unclear now). |
| 2025-11-19 10:23:10 +0100 | chromoblob | (~chromoblo@user/chromob1ot1c) chromoblob\0 |
| 2025-11-19 10:19:28 +0100 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-11-19 10:09:30 +0100 | ft | (~ft@p4fc2aaeb.dip0.t-ipconnect.de) (Quit: leaving) |
| 2025-11-19 10:07:16 +0100 | fp | (~Thunderbi@wireless-86-50-140-28.open.aalto.fi) (Ping timeout: 264 seconds) |
| 2025-11-19 09:54:03 +0100 | deptype | (~deptype@2406:b400:3a:9d2f:51eb:3f10:3160:250) |
| 2025-11-19 09:53:38 +0100 | deptype | (~deptype@2406:b400:3a:9d2f:bc3f:db4e:595e:ce22) (Remote host closed the connection) |
| 2025-11-19 09:53:14 +0100 | annamalai | (~annamalai@157.33.241.221) annamalai |