Newest at the top
| 2026-05-30 23:43:34 +0000 | <lisbeths> | and my lazy way of doing this is with a relational db |
| 2026-05-30 23:43:17 +0000 | <lisbeths> | so generally you want to do some optimizations when interpreting lambda calculus to reduce the number of beta reductions for common algorithms |
| 2026-05-30 23:43:12 +0000 | phos | (~az-181@2a04:4a43:94bf:f166:33c0:fe4e:a468:67a4) |
| 2026-05-30 23:42:43 +0000 | <lisbeths> | well theres this really small lc interpreter called sectorlambda, and I am working on making my own. but the problem I run into is arrays in a non optimized lc interpreter have suboptimal array lookup times |
| 2026-05-30 23:42:33 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2026-05-30 23:42:06 +0000 | Pozyomka | (~pyon@user/pyon) pyon |
| 2026-05-30 23:41:47 +0000 | Pozyomka | (~pyon@user/pyon) (Remote host closed the connection) |
| 2026-05-30 23:41:27 +0000 | phos | (~az-181@2a04:4a43:94bf:f166:33c0:fe4e:a468:67a4) (Ping timeout: 252 seconds) |
| 2026-05-30 23:37:59 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-30 23:33:23 +0000 | Inline | (~noOne@ipservice-092-208-182-236.092.208.pools.vodafone-ip.de) (Ping timeout: 247 seconds) |
| 2026-05-30 23:33:08 +0000 | <yin> | now i'm thinking that a lambda bar would be much more useful than a space bar when typing LC |
| 2026-05-30 23:26:42 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2026-05-30 23:25:49 +0000 | Pozyomka | (~pyon@user/pyon) pyon |
| 2026-05-30 23:25:35 +0000 | Pozyomka | (~pyon@user/pyon) (Remote host closed the connection) |
| 2026-05-30 23:20:04 +0000 | <Clint> | i'm surprised that's not the name of a bar somewhere |
| 2026-05-30 23:19:55 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-30 23:18:36 +0000 | <monochrom> | On the bright side "the Lambda Room" would be a cute name. >:) |
| 2026-05-30 23:17:27 +0000 | <monochrom> | Both that scheme and John Searle's Chinese Room argument are ignoring the cold hard reality that search becomes slower than computation as soon as your database becomes large enough to answer all questions that occur in practice. |
| 2026-05-30 23:17:18 +0000 | vanishingideal | (~vanishing@user/vanishingideal) vanishingideal |
| 2026-05-30 23:10:56 +0000 | Pozyomka | (~pyon@user/pyon) pyon |
| 2026-05-30 23:10:47 +0000 | Pozyomka | (~pyon@user/pyon) (Remote host closed the connection) |
| 2026-05-30 23:09:07 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 258 seconds) |
| 2026-05-30 23:04:28 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-30 22:53:36 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2026-05-30 22:52:50 +0000 | <dolio> | What are you doing now? |
| 2026-05-30 22:50:49 +0000 | target_i | (~target_i@user/target-i/x-6023099) (Quit: leaving) |
| 2026-05-30 22:49:49 +0000 | <lisbeths> | what can I do to speed up the performance of a pure lambda calculus machine. thus far my only thought has been to code it into a relational database so that computations get cached |
| 2026-05-30 22:49:28 +0000 | amish | astra |
| 2026-05-30 22:48:59 +0000 | amish | (sid289983@user/amish) amish |
| 2026-05-30 22:48:59 +0000 | amish | (sid289983@id-289983.hampstead.irccloud.com) (Changing host) |
| 2026-05-30 22:48:55 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-30 22:48:54 +0000 | Guest3503 | amish |
| 2026-05-30 22:45:56 +0000 | __monty__ | (~toonn@user/toonn) (Quit: leaving) |
| 2026-05-30 22:44:39 +0000 | amish | Guest3503 |
| 2026-05-30 22:44:09 +0000 | astra | amish |
| 2026-05-30 22:38:03 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 263 seconds) |
| 2026-05-30 22:35:27 +0000 | yin | (~zero@user/zero) zero |
| 2026-05-30 22:33:12 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-30 22:22:34 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 262 seconds) |
| 2026-05-30 22:20:56 +0000 | haritz | (~hrtz@user/haritz) haritz |
| 2026-05-30 22:20:56 +0000 | haritz | (~hrtz@2a01:4b00:bc2e:7000:d5af:a266:ca31:5ef8) (Changing host) |
| 2026-05-30 22:20:55 +0000 | haritz | (~hrtz@2a01:4b00:bc2e:7000:d5af:a266:ca31:5ef8) |
| 2026-05-30 22:19:01 +0000 | synchromesh | (~john@2406:5a00:247e:1500:9a0:33e6:ebb2:ef41) synchromesh |
| 2026-05-30 22:18:22 +0000 | takuan | (~takuan@d8D86B9E9.access.telenet.be) (Ping timeout: 247 seconds) |
| 2026-05-30 22:17:58 +0000 | synchromesh | (~john@2406:5a00:247e:1500:b15f:a188:70f5:85a4) (Read error: Connection reset by peer) |
| 2026-05-30 22:17:24 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-30 22:17:18 +0000 | vanishingideal | (~vanishing@user/vanishingideal) (Ping timeout: 252 seconds) |
| 2026-05-30 22:16:28 +0000 | yin | (~zero@user/zero) (Ping timeout: 276 seconds) |
| 2026-05-30 22:13:05 +0000 | Hafydd | (~Hafydd@user/hafydd) (Quit: WeeChat 4.8.1) |
| 2026-05-30 22:11:59 +0000 | Pozyomka | (~pyon@user/pyon) pyon |