Newest at the top
| 2025-04-10 10:04:33 +0200 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) (Ping timeout: 248 seconds) |
| 2025-04-10 09:57:30 +0200 | machinedgod | (~machinedg@d108-173-18-100.abhsia.telus.net) machinedgod |
| 2025-04-10 09:53:45 +0200 | ski | . o O ( "Interview with Vibe Coder in 2025" <https://www.youtube.com/watch?v=JeNS1ZNHQs8> ) |
| 2025-04-10 09:53:30 +0200 | fp | (~Thunderbi@2001:708:20:1406::1370) fp |
| 2025-04-10 09:49:38 +0200 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-04-10 09:45:38 +0200 | lisbeths | (uid135845@id-135845.lymington.irccloud.com) lisbeths |
| 2025-04-10 09:41:08 +0200 | Sgeo | (~Sgeo@user/sgeo) (Read error: Connection reset by peer) |
| 2025-04-10 09:40:00 +0200 | XZDX | (~xzdx@2601:404:ce00:4e51:214:51ff:fe2b:e82e) |
| 2025-04-10 09:39:43 +0200 | XZDX | (~xzdx@user/XZDX) (Remote host closed the connection) |
| 2025-04-10 09:36:43 +0200 | acidjnk | (~acidjnk@p200300d6e71c4f74c570287c99ce2cc6.dip0.t-ipconnect.de) acidjnk |
| 2025-04-10 09:35:37 +0200 | lortabac | (~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) lortabac |
| 2025-04-10 09:29:41 +0200 | chele | (~chele@user/chele) chele |
| 2025-04-10 09:23:53 +0200 | remedan | (~remedan@ip-62-245-108-153.bb.vodafone.cz) remedan |
| 2025-04-10 09:23:03 +0200 | <[exa]> | (nvm, opened an issue here if someone's interested in poking in that https://github.com/AccelerateHS/accelerate-llvm/issues/102 ) |
| 2025-04-10 09:19:50 +0200 | Lord_of_Life_ | Lord_of_Life |
| 2025-04-10 09:19:12 +0200 | vpan | (~vpan@212.117.1.172) |
| 2025-04-10 09:18:26 +0200 | Lord_of_Life_ | (~Lord@user/lord-of-life/x-2819915) Lord_of_Life |
| 2025-04-10 09:18:18 +0200 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) (Ping timeout: 245 seconds) |
| 2025-04-10 09:15:44 +0200 | TMA | (tma@twin.jikos.cz) (Ping timeout: 260 seconds) |
| 2025-04-10 09:15:06 +0200 | remedan | (~remedan@ip-62-245-108-153.bb.vodafone.cz) (Ping timeout: 252 seconds) |
| 2025-04-10 09:09:02 +0200 | <[exa]> | somehow I can't even trace how ghc comes to executing the C source |
| 2025-04-10 09:08:48 +0200 | <[exa]> | In particular I've got this thing here with accelerate-llvm: https://paste.tomsmeding.com/GbdNItS1 |
| 2025-04-10 09:08:33 +0200 | <[exa]> | Is there any good way how to debug assertion failure in C++ code that get somehow (no idea how) triggered from usual ghc compilation? |
| 2025-04-10 09:05:20 +0200 | inca | (~inca@pool-96-255-212-224.washdc.fios.verizon.net) |
| 2025-04-10 09:04:52 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 272 seconds) |
| 2025-04-10 09:03:09 +0200 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) |
| 2025-04-10 09:01:03 +0200 | caconym | (~caconym@user/caconym) caconym |
| 2025-04-10 09:00:04 +0200 | caconym | (~caconym@user/caconym) (Quit: bye) |
| 2025-04-10 08:59:14 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-04-10 08:57:16 +0200 | CiaoSen | (~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen |
| 2025-04-10 08:57:11 +0200 | inca | (~inca@pool-96-255-212-224.washdc.fios.verizon.net) (Ping timeout: 244 seconds) |
| 2025-04-10 08:51:52 +0200 | inca | (~inca@pool-96-255-212-224.washdc.fios.verizon.net) |
| 2025-04-10 08:50:37 +0200 | tromp | (~textual@2001:1c00:3487:1b00:44ed:cdbe:8e8e:71c5) |
| 2025-04-10 08:48:21 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2025-04-10 08:48:07 +0200 | ft | (~ft@p508db594.dip0.t-ipconnect.de) (Quit: leaving) |
| 2025-04-10 08:47:44 +0200 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) (Ping timeout: 260 seconds) |
| 2025-04-10 08:43:29 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-04-10 08:42:58 +0200 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) |
| 2025-04-10 08:37:57 +0200 | inca | (~inca@pool-96-255-212-224.washdc.fios.verizon.net) (Ping timeout: 246 seconds) |
| 2025-04-10 08:32:28 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2025-04-10 08:31:00 +0200 | foul_owl | (~kerry@94.156.149.97) foul_owl |
| 2025-04-10 08:28:51 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 246 seconds) |
| 2025-04-10 08:27:39 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-04-10 08:24:19 +0200 | <haskellbridge> | <hellwolf> i get it now. thanks for explaining. |
| 2025-04-10 08:24:13 +0200 | <haskellbridge> | <hellwolf> but it had nothing to do with it. |
| 2025-04-10 08:24:04 +0200 | <haskellbridge> | <hellwolf> it was an illusion that it looked like a type declaration |
| 2025-04-10 08:23:22 +0200 | <haskellbridge> | So if I run it through the TH, it would show the right syntax constructor and makes sense. |
| 2025-04-10 08:23:22 +0200 | <haskellbridge> | <hellwolf> now it starts to make sense, it's a pattern matching. |
| 2025-04-10 08:22:49 +0200 | <Leary> | ScopedTypeVariables. It simply isn't intended to replace top-level type signatures. |
| 2025-04-10 08:22:33 +0200 | jmcantrell_ | jmcantrell |