Newest at the top
| 2025-01-27 17:28:14 +0100 | Fijxu | (~Fijxu@user/fijxu) fijxu |
| 2025-01-27 17:27:19 +0100 | ft | (~ft@p3e9bcd97.dip0.t-ipconnect.de) ft |
| 2025-01-27 17:17:48 +0100 | Fijxu | (~Fijxu@user/fijxu) (Ping timeout: 244 seconds) |
| 2025-01-27 17:11:54 +0100 | lortabac | (~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) (Quit: WeeChat 4.4.2) |
| 2025-01-27 17:10:46 +0100 | hueso | (~root@user/hueso) (Quit: hueso) |
| 2025-01-27 17:10:24 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 252 seconds) |
| 2025-01-27 17:05:57 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-01-27 17:03:48 +0100 | alecs | (~alecs@nat16.software.imdea.org) (Ping timeout: 252 seconds) |
| 2025-01-27 17:02:06 +0100 | fp | (~Thunderbi@2001:708:150:10::7390) (Ping timeout: 246 seconds) |
| 2025-01-27 16:53:31 +0100 | simplystuart | (~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) (Ping timeout: 244 seconds) |
| 2025-01-27 16:53:24 +0100 | Miroboru | (~myrvoll@178-164-114.82.3p.ntebredband.no) Miroboru |
| 2025-01-27 16:49:15 +0100 | simplystuart | (~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) |
| 2025-01-27 16:48:36 +0100 | acidjnk | (~acidjnk@p200300d6e7283f58c43e5382bd47b9f2.dip0.t-ipconnect.de) acidjnk |
| 2025-01-27 16:45:45 +0100 | simplystuart | (~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) (Ping timeout: 276 seconds) |
| 2025-01-27 16:41:10 +0100 | euleritian | (~euleritia@ip4d17fae8.dynamic.kabel-deutschland.de) |
| 2025-01-27 16:40:46 +0100 | simplystuart | (~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) |
| 2025-01-27 16:40:20 +0100 | euleritian | (~euleritia@ip4d17fae8.dynamic.kabel-deutschland.de) (Read error: Connection reset by peer) |
| 2025-01-27 16:38:08 +0100 | euleritian | (~euleritia@ip4d17fae8.dynamic.kabel-deutschland.de) |
| 2025-01-27 16:37:49 +0100 | euleritian | (~euleritia@dynamic-176-006-143-130.176.6.pool.telefonica.de) (Read error: Connection reset by peer) |
| 2025-01-27 16:36:39 +0100 | acidjnk | (~acidjnk@p200300d6e7283f58c4cea7af3a5e8af9.dip0.t-ipconnect.de) (Ping timeout: 252 seconds) |
| 2025-01-27 16:33:10 +0100 | tnt1 | (~Thunderbi@user/tnt1) (Remote host closed the connection) |
| 2025-01-27 16:27:58 +0100 | caubert_ | caubert |
| 2025-01-27 16:26:50 +0100 | JuanDaugherty | (~juan@user/JuanDaugherty) (Quit: praxis.meansofproduction.biz (juan@acm.org)) |
| 2025-01-27 16:24:59 +0100 | simplystuart | (~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) (Ping timeout: 260 seconds) |
| 2025-01-27 16:21:37 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 252 seconds) |
| 2025-01-27 16:20:05 +0100 | jcarpenter2 | (~lol@2603:3016:1e01:b9c0:f81e:e0f5:bc3d:aa5) |
| 2025-01-27 16:18:22 +0100 | JuanDaugherty | (~juan@user/JuanDaugherty) JuanDaugherty |
| 2025-01-27 16:18:04 +0100 | simplystuart | (~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) |
| 2025-01-27 16:17:13 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-01-27 16:13:57 +0100 | Smiles | (uid551636@id-551636.lymington.irccloud.com) Smiles |
| 2025-01-27 16:11:33 +0100 | alp_ | (~alp@2001:861:8ca0:4940:e570:5962:9fdf:417e) |
| 2025-01-27 16:05:03 +0100 | Miroboru | (~myrvoll@178-164-114.82.3p.ntebredband.no) (Ping timeout: 246 seconds) |
| 2025-01-27 16:03:46 +0100 | alp_ | (~alp@128-79-174-146.hfc.dyn.abo.bbox.fr) (Ping timeout: 248 seconds) |
| 2025-01-27 15:55:37 +0100 | euleritian | (~euleritia@dynamic-176-006-143-130.176.6.pool.telefonica.de) |
| 2025-01-27 15:54:39 +0100 | euleritian | (~euleritia@77.23.250.232) (Ping timeout: 260 seconds) |
| 2025-01-27 15:54:14 +0100 | <euouae> | makes sense, thank you |
| 2025-01-27 15:51:21 +0100 | <__monty__> | euouae: You'd probably just use `parse` in a testsuite. |
| 2025-01-27 15:50:38 +0100 | <haskellbridge> | <sm> https://markkarpov.com/tutorial/megaparsec.html#testing-megaparsec-parsers ? |
| 2025-01-27 15:50:36 +0100 | <__monty__> | euouae: That function's more intended for interactive "testing", like in the repl. |
| 2025-01-27 15:49:59 +0100 | <haskellbridge> | <sm> https://markkarpov.com/posts has the blog posts I was thinking of. They're not really beginner oriented but I think they can be helpful to give an idea of the evolution and why things are as they are now |
| 2025-01-27 15:48:37 +0100 | <euouae> | the parseTest function is not appropriate since it just prints stuff in failure but the test checks pass |
| 2025-01-27 15:48:13 +0100 | <euouae> | Another thing I can't figure out is how to use megaparsec in a test suite |
| 2025-01-27 15:47:29 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Quit: = "") |
| 2025-01-27 15:47:05 +0100 | <haskellbridge> | <sm> I mean: the flatparse docs look fairly minimal. That's something I appreciated about mp |
| 2025-01-27 15:46:31 +0100 | <haskellbridge> | <sm> (need.. as a person who struggled with parsers :) |
| 2025-01-27 15:46:21 +0100 | simplystuart | (~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) (Ping timeout: 252 seconds) |
| 2025-01-27 15:46:11 +0100 | <haskellbridge> | <sm> I don't know what flatparse has, so I'm just picking your brains in case I'm missing something better. Docs are certainly not what I'd want |
| 2025-01-27 15:45:36 +0100 | <haskellbridge> | <sm> I hear that. For me it's more than that, it's also things like practical api already there for real world needs, good maintenance, good ecosystem support, and especially excellent documentation |
| 2025-01-27 15:45:26 +0100 | <__monty__> | Do you use flatparse with the parser-combinators package? |
| 2025-01-27 15:44:49 +0100 | <dminuoso> | Where `merge` is just a function to merge an inner and outer error together in a sensible fashion |