Newest at the top
| 2025-05-04 19:11:39 +0200 | econo_ | (uid147250@id-147250.tinside.irccloud.com) |
| 2025-05-04 19:09:46 +0200 | tromp | (~textual@2001:1c00:3487:1b00:25b8:e34c:8097:c1c7) |
| 2025-05-04 19:08:10 +0200 | Sgeo | (~Sgeo@user/sgeo) Sgeo |
| 2025-05-04 19:08:06 +0200 | tromp | (~textual@2001:1c00:3487:1b00:25b8:e34c:8097:c1c7) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2025-05-04 19:07:37 +0200 | <hellwolf> | actually, sometimes I see the "expected" and "actual" words, sometimes I don't. |
| 2025-05-04 19:07:20 +0200 | <hellwolf> | since when |
| 2025-05-04 19:07:05 +0200 | euleritian | (~euleritia@ip4d17f82f.dynamic.kabel-deutschland.de) |
| 2025-05-04 19:07:00 +0200 | <lambdabot> | • In the expression: () |
| 2025-05-04 19:07:00 +0200 | <lambdabot> | • Couldn't match expected type ‘Bool’ with actual type ‘()’ |
| 2025-05-04 19:07:00 +0200 | <lambdabot> | error: |
| 2025-05-04 19:06:59 +0200 | <int-e> | > let False = () in () |
| 2025-05-04 19:06:47 +0200 | euleritian | (~euleritia@dynamic-176-006-131-173.176.6.pool.telefonica.de) (Read error: Connection reset by peer) |
| 2025-05-04 19:06:41 +0200 | <int-e> | ah no |
| 2025-05-04 19:06:29 +0200 | <lambdabot> | • In the expression: b |
| 2025-05-04 19:06:29 +0200 | <lambdabot> | • Occurs check: cannot construct the infinite type: a ~ (a, b) |
| 2025-05-04 19:06:29 +0200 | <lambdabot> | error: |
| 2025-05-04 19:06:27 +0200 | <int-e> | > let b = (b,b) in () |
| 2025-05-04 19:06:06 +0200 | euleritian | (~euleritia@dynamic-176-006-131-173.176.6.pool.telefonica.de) |
| 2025-05-04 19:05:39 +0200 | euleritian | (~euleritia@77.23.248.47) (Ping timeout: 244 seconds) |
| 2025-05-04 19:04:00 +0200 | <hellwolf> | I always have trouble reading this sentence: Which one was expected, and which one was actual? |
| 2025-05-04 19:04:00 +0200 | <hellwolf> | | Couldn't match type ‘BOOL’ with ‘(BOOL, b10)’ |
| 2025-05-04 19:03:45 +0200 | acidjnk_new3 | (~acidjnk@p200300d6e71c4f524d98fe298d45bbdf.dip0.t-ipconnect.de) (Ping timeout: 272 seconds) |
| 2025-05-04 19:03:28 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
| 2025-05-04 19:00:52 +0200 | ystael | (~ystael@user/ystael) ystael |
| 2025-05-04 18:59:31 +0200 | Guest70 | (~Guest80@82.153.135.43) (Client Quit) |
| 2025-05-04 18:58:47 +0200 | ttybitnik | (~ttybitnik@user/wolper) (Remote host closed the connection) |
| 2025-05-04 18:58:01 +0200 | Guest70 | (~Guest80@82.153.135.43) |
| 2025-05-04 18:57:29 +0200 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 268 seconds) |
| 2025-05-04 18:56:03 +0200 | tzh | (~tzh@c-76-115-131-146.hsd1.or.comcast.net) |
| 2025-05-04 18:55:19 +0200 | Arpad | (~Arpad@2a02:ab88:38d:4700::b0d5) |
| 2025-05-04 18:46:44 +0200 | euphores | (~SASL_euph@user/euphores) euphores |
| 2025-05-04 18:43:44 +0200 | ChaiTRex | (~ChaiTRex@user/chaitrex) ChaiTRex |
| 2025-05-04 18:42:23 +0200 | __jmcantrell__ | (~weechat@user/jmcantrell) jmcantrell |
| 2025-05-04 18:42:19 +0200 | euleritian | (~euleritia@77.23.248.47) |
| 2025-05-04 18:42:12 +0200 | ChaiTRex | (~ChaiTRex@user/chaitrex) (Ping timeout: 264 seconds) |
| 2025-05-04 18:41:39 +0200 | euleritian | (~euleritia@77.23.248.47) (Read error: Connection reset by peer) |
| 2025-05-04 18:40:05 +0200 | euleritian | (~euleritia@77.23.248.47) |
| 2025-05-04 18:39:47 +0200 | euleritian | (~euleritia@dynamic-176-006-131-173.176.6.pool.telefonica.de) (Read error: Connection reset by peer) |
| 2025-05-04 18:38:33 +0200 | <EvanR> | I'm ok if Data.Map's implementation is packed with esoteric constants and jiggery pokery if it means more performance and I never have to mess with it xD |
| 2025-05-04 18:35:22 +0200 | euphores | (~SASL_euph@user/euphores) (Quit: Leaving.) |
| 2025-05-04 18:29:13 +0200 | <geekosaur> | and, uh, look at the implementation. they're usually pretty expensive. I mean, even a list zipper turns one list into two plus a lot of pushing and popping |
| 2025-05-04 18:27:58 +0200 | <Pozyomka> | Wow, and there's magical constants in the code too... |
| 2025-05-04 18:27:03 +0200 | <int-e> | that said, yes, zippers are heavy machinery in the sense that they tend to require a lot of code for non-trivial data structures |
| 2025-05-04 18:26:36 +0200 | <int-e> | and as far as I can tell, that was introduced just for the benefit of alterF |
| 2025-05-04 18:26:21 +0200 | <Pozyomka> | Wow, that's just... bonkers. |
| 2025-05-04 18:25:44 +0200 | <int-e> | it remembers a path in a bit mask |
| 2025-05-04 18:25:23 +0200 | <int-e> | Pozyomka: there's no zipper |
| 2025-05-04 18:20:50 +0200 | j1n37 | (~j1n37@user/j1n37) j1n37 |
| 2025-05-04 18:19:23 +0200 | <Pozyomka> | int-e: “pretty heavy machinery” -- Are zippers heavy machinery now? |
| 2025-05-04 18:18:42 +0200 | CiaoSen | (~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) (Ping timeout: 276 seconds) |