Newest at the top
| 2026-04-09 18:23:14 +0000 | PaulMartensen | (15a119e437@2001:bc8:1210:2cd8::3bc) (Ping timeout: 245 seconds) |
| 2026-04-09 18:20:38 +0000 | Typosit | (b41a81e702@2001:bc8:1210:2cd8::494) (Ping timeout: 244 seconds) |
| 2026-04-09 18:19:03 +0000 | PaulMartensen | (15a119e437@2001:bc8:1210:2cd8::3bc) |
| 2026-04-09 18:16:23 +0000 | Typosit | (b41a81e702@2001:bc8:1210:2cd8::494) |
| 2026-04-09 18:15:21 +0000 | Ging | (46fea76d80@2001:bc8:1210:2cd8::470) (Ping timeout: 272 seconds) |
| 2026-04-09 18:13:53 +0000 | GdeVolpiano | (~GdeVolpia@user/GdeVolpiano) GdeVolpiano |
| 2026-04-09 18:12:43 +0000 | Googulator | (~Googulato@94-21-172-213.pool.digikabel.hu) |
| 2026-04-09 18:12:36 +0000 | Typosit | (b41a81e702@2001:bc8:1210:2cd8::494) (Ping timeout: 246 seconds) |
| 2026-04-09 18:12:12 +0000 | Googulator | (~Googulato@94-21-172-213.pool.digikabel.hu) (Quit: Client closed) |
| 2026-04-09 18:09:16 +0000 | PaulMartensen | (15a119e437@2001:bc8:1210:2cd8::3bc) (Ping timeout: 244 seconds) |
| 2026-04-09 18:08:50 +0000 | GdeVolpiano | (~GdeVolpia@user/GdeVolpiano) (Quit: WeeChat 4.7.2) |
| 2026-04-09 18:08:24 +0000 | Ging | (46fea76d80@2001:bc8:1210:2cd8::470) |
| 2026-04-09 18:08:10 +0000 | Typosit | (b41a81e702@2001:bc8:1210:2cd8::494) |
| 2026-04-09 18:05:19 +0000 | danz90119 | (~danza@user/danza) (Remote host closed the connection) |
| 2026-04-09 18:04:54 +0000 | PaulMartensen | (15a119e437@2001:bc8:1210:2cd8::3bc) |
| 2026-04-09 18:04:35 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 272 seconds) |
| 2026-04-09 18:04:33 +0000 | mikess | (~sam@user/mikess) (Quit: leaving) |
| 2026-04-09 18:01:25 +0000 | PaulMartensen | (15a119e437@2001:bc8:1210:2cd8::3bc) (Ping timeout: 272 seconds) |
| 2026-04-09 18:00:20 +0000 | Enrico63 | (~Enrico63@host-212-171-80-94.retail.telecomitalia.it) Enrico63 |
| 2026-04-09 17:59:42 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-09 17:58:56 +0000 | Typosit | (b41a81e702@2001:bc8:1210:2cd8::494) (Ping timeout: 244 seconds) |
| 2026-04-09 17:58:39 +0000 | uli-fem | (~uli-fem@115.128.112.118) (Ping timeout: 255 seconds) |
| 2026-04-09 17:56:27 +0000 | PaulMartensen | (15a119e437@2001:bc8:1210:2cd8::3bc) |
| 2026-04-09 17:54:44 +0000 | Typosit | (b41a81e702@2001:bc8:1210:2cd8::494) |
| 2026-04-09 17:53:58 +0000 | uli-fem | (~uli-fem@115.128.112.118) |
| 2026-04-09 17:52:04 +0000 | tromp | (~textual@2001:1c00:340e:2700:8dcf:a6d6:339b:7a0) |
| 2026-04-09 17:51:05 +0000 | Typosit | (b41a81e702@2001:bc8:1210:2cd8::494) (Ping timeout: 244 seconds) |
| 2026-04-09 17:48:25 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2026-04-09 17:47:54 +0000 | ft | (~ft@p508db287.dip0.t-ipconnect.de) ft |
| 2026-04-09 17:47:27 +0000 | <monochrom> | Corollary: "strict vs lazy" is comparing apples with cells. |
| 2026-04-09 17:47:12 +0000 | qqq | (~qqq@194.124.210.29) (Quit: leaving) |
| 2026-04-09 17:47:07 +0000 | jmcantrell | (~weechat@user/jmcantrell) (Ping timeout: 264 seconds) |
| 2026-04-09 17:47:03 +0000 | PaulMartensen | (15a119e437@2001:bc8:1210:2cd8::3bc) (Ping timeout: 244 seconds) |
| 2026-04-09 17:47:02 +0000 | <monochrom> | i.e., non-strict is denotational, evaluation order is operational. |
| 2026-04-09 17:46:41 +0000 | Typosit | (b41a81e702@2001:bc8:1210:2cd8::494) |
| 2026-04-09 17:46:33 +0000 | <monochrom> | Non-strict just says: const 5 undefined = 5, I don't care how you pull it off. Evaluation order says how to pull it off. |
| 2026-04-09 17:45:52 +0000 | <danz90119> | meh |
| 2026-04-09 17:45:25 +0000 | <monochrom> | Not even at the same level of abstraction! |
| 2026-04-09 17:45:08 +0000 | <danz90119> | then the two terms are not equivalent... |
| 2026-04-09 17:44:43 +0000 | <monochrom> | Yes. Mine is not call by name. |
| 2026-04-09 17:44:17 +0000 | <danz90119> | am i wrong or non-strict evaluation could be called simply call by name? |
| 2026-04-09 17:43:23 +0000 | <monochrom> | My favourite non-strict evaluation order is crazy evaluation. Other people know it as speculative evaluation. To evaluate `f x`, fork two threads, one evaluates f and the other evalutates x, and you are ready to throw away the latter if you find out that you don't need it. |
| 2026-04-09 17:42:36 +0000 | PaulMartensen | (15a119e437@2001:bc8:1210:2cd8::3bc) |
| 2026-04-09 17:41:43 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-09 17:41:35 +0000 | <monochrom> | (Belated) Strictly (pun!) speaking, Haskell spec doesn't even require lazy evaluation, only non-strictness (see? >:) ). |
| 2026-04-09 17:41:27 +0000 | Typosit | (b41a81e702@2001:bc8:1210:2cd8::494) (Ping timeout: 246 seconds) |
| 2026-04-09 17:38:16 +0000 | PaulMartensen | (15a119e437@2001:bc8:1210:2cd8::3bc) (Ping timeout: 268 seconds) |
| 2026-04-09 17:37:39 +0000 | Ging | (46fea76d80@2001:bc8:1210:2cd8::470) (Ping timeout: 268 seconds) |
| 2026-04-09 17:36:56 +0000 | Typosit | (b41a81e702@2001:bc8:1210:2cd8::494) |
| 2026-04-09 17:35:07 +0000 | tromp | (~textual@2001:1c00:340e:2700:8dcf:a6d6:339b:7a0) (Quit: My iMac has gone to sleep. ZZZzzz…) |