Logs: liberachat/#haskell
| 2021-06-04 06:29:16 | → | lavaman joins (~lavaman@98.38.249.169) |
| 2021-06-04 06:31:02 | → | lortabac joins (~lortabac@2a01:e0a:541:b8f0:2510:e0bc:659d:298) |
| 2021-06-04 06:31:22 | ← | antalsz parts (~antalsz@68.175.130.216) () |
| 2021-06-04 06:32:38 | → | ddellaco_ joins (~ddellacos@89.46.62.86) |
| 2021-06-04 06:33:50 | → | wonko joins (~wjc@62.115.229.50) |
| 2021-06-04 06:34:24 | × | lavaman quits (~lavaman@98.38.249.169) (Ping timeout: 272 seconds) |
| 2021-06-04 06:35:44 | → | opqdonut joins (opqdonut@pseudo.fixme.fi) |
| 2021-06-04 06:37:34 | × | ddellaco_ quits (~ddellacos@89.46.62.86) (Ping timeout: 272 seconds) |
| 2021-06-04 06:45:10 | × | node-sh quits (~node-sh@2401:4900:3b29:78ba:5b23:3841:af60:74fd) (Ping timeout: 272 seconds) |
| 2021-06-04 06:46:21 | → | node-sh joins (~node-sh@223.228.233.174) |
| 2021-06-04 06:48:05 | <dminuoso> | `AttoParsec.parseOnly (f <> pure Foo)` can this possibly error out? |
| 2021-06-04 06:48:18 | <dminuoso> | err. |
| 2021-06-04 06:48:24 | <dminuoso> | `AttoParsec.parseOnly (f <|> pure Foo)` of course! :) |
| 2021-06-04 06:53:22 | → | marinelli joins (~marinelli@gateway/tor-sasl/marinelli) |
| 2021-06-04 06:53:51 | × | echoreply quits (~echoreply@2001:19f0:9002:1f3b:5400:ff:fe6f:8b8d) (Quit: WeeChat 1.9.1) |
| 2021-06-04 06:54:19 | → | echoreply joins (~echoreply@45.32.163.16) |
| 2021-06-04 06:54:31 | → | epolanski joins (uid312403@id-312403.brockwell.irccloud.com) |
| 2021-06-04 06:56:04 | → | dhouthoo joins (~dhouthoo@178-117-36-167.access.telenet.be) |
| 2021-06-04 06:56:41 | × | ddellacosta quits (~ddellacos@86.106.143.235) (Remote host closed the connection) |
| 2021-06-04 06:56:47 | → | jco joins (~jco@c83-248-173-38.bredband.tele2.se) |
| 2021-06-04 06:56:54 | → | ddellacosta joins (~ddellacos@86.106.143.235) |
| 2021-06-04 06:57:29 | × | ddellacosta quits (~ddellacos@86.106.143.235) (Remote host closed the connection) |
| 2021-06-04 06:57:31 | → | michalz joins (~user@185.246.204.60) |
| 2021-06-04 06:58:25 | × | jco quits (~jco@c83-248-173-38.bredband.tele2.se) (Client Quit) |
| 2021-06-04 06:58:31 | <hololeap> | I don't think `pure x` ever fails |
| 2021-06-04 06:59:14 | <hololeap> | AttoParsec.parseOnly (Foo <$ f) -- this might be what you want, dminuoso |
| 2021-06-04 07:00:28 | <hololeap> | eh, maybe not |
| 2021-06-04 07:01:28 | <dminuoso> | Heh :) |
| 2021-06-04 07:01:42 | <dminuoso> | Nah, I was merely wondering whether acting on the resulting parse error was necessary |
| 2021-06-04 07:01:47 | <dminuoso> | If not, Ill just trigger a panic |
| 2021-06-04 07:02:00 | <dminuoso> | saves me from threading a silly error out of some deeply nested code |
| 2021-06-04 07:05:38 | × | hololeap quits (hololeap@user/hololeap) (Quit: Bye) |
| 2021-06-04 07:07:26 | × | wonko quits (~wjc@62.115.229.50) (Changing host) |
| 2021-06-04 07:07:26 | → | wonko joins (~wjc@user/wonko) |
| 2021-06-04 07:07:45 | → | ddellacosta joins (~ddellacos@89.46.62.87) |
| 2021-06-04 07:07:58 | → | bor0 joins (~boro@user/bor0) |
| 2021-06-04 07:08:17 | → | mpt joins (~tom@p57a566da.dip0.t-ipconnect.de) |
| 2021-06-04 07:12:00 | × | ddellacosta quits (~ddellacos@89.46.62.87) (Ping timeout: 245 seconds) |
| 2021-06-04 07:13:05 | × | mpt quits (~tom@p57a566da.dip0.t-ipconnect.de) (Ping timeout: 272 seconds) |
| 2021-06-04 07:14:03 | → | bfrk joins (~Thunderbi@200116b845d01a0023133a647a2f786d.dip.versatel-1u1.de) |
| 2021-06-04 07:15:28 | → | ixlun joins (~matthew@109.249.184.235) |
| 2021-06-04 07:21:08 | × | aweinstock quits (~aweinstoc@cpe-67-248-65-250.nycap.res.rr.com) (Ping timeout: 252 seconds) |
| 2021-06-04 07:21:39 | → | ddellacosta joins (~ddellacos@89.45.224.40) |
| 2021-06-04 07:23:07 | → | fendor joins (~fendor@178.115.129.101.wireless.dyn.drei.com) |
| 2021-06-04 07:27:22 | → | ddellaco_ joins (~ddellacos@86.106.121.77) |
| 2021-06-04 07:28:55 | × | phma quits (phma@2001:5b0:2172:da08:98fc:87:ee60:b793) (Read error: Connection reset by peer) |
| 2021-06-04 07:31:49 | → | koishi_ joins (~koishi_@185.209.85.134) |
| 2021-06-04 07:31:55 | <ukari> | if I define a `type Allocator m a = forall r . (m a -> (a -> m ()) -> r) -> r`, which module should it be put in? like `module Types`, `module Type` or `module Util`? |
| 2021-06-04 07:32:02 | × | ddellaco_ quits (~ddellacos@86.106.121.77) (Ping timeout: 272 seconds) |
| 2021-06-04 07:32:07 | × | amk quits (~amk@176.61.106.150) (Read error: Connection reset by peer) |
| 2021-06-04 07:32:19 | <dminuoso> | ukari: Up to you. |
| 2021-06-04 07:32:56 | <ukari> | hard to decide |
| 2021-06-04 07:33:26 | → | amk joins (~amk@176.61.106.150) |
| 2021-06-04 07:34:13 | → | dpl joins (~dpl@77-121-78-163.chn.volia.net) |
| 2021-06-04 07:34:19 | → | cfricke joins (~cfricke@user/cfricke) |
| 2021-06-04 07:36:05 | × | fabfianda quits (~fabfianda@net-93-148-121-206.cust.dsl.teletu.it) (Ping timeout: 244 seconds) |
| 2021-06-04 07:36:56 | → | fabfianda joins (~fabfianda@mob-5-90-247-167.net.vodafone.it) |
| 2021-06-04 07:37:26 | → | gehmehgeh joins (~user@user/gehmehgeh) |
| 2021-06-04 07:40:40 | → | dunkeln joins (~dunkeln@94.129.65.28) |
| 2021-06-04 07:40:50 | × | Sgeo quits (~Sgeo@user/sgeo) (Read error: Connection reset by peer) |
| 2021-06-04 07:41:57 | × | amk quits (~amk@176.61.106.150) (Read error: Connection reset by peer) |
| 2021-06-04 07:42:34 | × | koishi_ quits (~koishi_@185.209.85.134) (Quit: /ragequit) |
| 2021-06-04 07:42:56 | → | amk joins (~amk@176.61.106.150) |
| 2021-06-04 07:45:22 | → | ddellaco_ joins (~ddellacos@89.46.62.44) |
| 2021-06-04 07:45:39 | → | phma joins (phma@2001:5b0:211f:f668:98fc:87:ee60:b793) |
| 2021-06-04 07:47:52 | → | scannow joins (~scannow@94.233.41.249) |
| 2021-06-04 07:47:53 | → | Guest91 joins (~Guest91@180.168.212.6) |
| 2021-06-04 07:48:41 | ← | scannow parts (~scannow@94.233.41.249) () |
| 2021-06-04 07:49:30 | × | ddellaco_ quits (~ddellacos@89.46.62.44) (Ping timeout: 245 seconds) |
| 2021-06-04 07:49:41 | × | Guest91 quits (~Guest91@180.168.212.6) (Client Quit) |
| 2021-06-04 07:53:07 | <beaky> | should error discouraged from use it seems it can lead to gotchas in evaluation order or soemthing (so you get different error messages) https://gitlab.haskell.org/ghc/ghc/-/issues/19917 |
| 2021-06-04 07:55:10 | × | hnOsmium0001 quits (uid453710@id-453710.stonehaven.irccloud.com) (Quit: Connection closed for inactivity) |
| 2021-06-04 07:58:02 | × | tzh quits (~tzh@c-24-21-73-154.hsd1.or.comcast.net) (Quit: zzz) |
| 2021-06-04 07:59:42 | × | werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 264 seconds) |
| 2021-06-04 07:59:56 | → | werneta joins (~werneta@128.149.243.107) |
| 2021-06-04 08:00:09 | → | merijn joins (~merijn@83-160-49-249.ip.xs4all.nl) |
| 2021-06-04 08:00:57 | → | Guest38 joins (~textual@188-182-241-27-dynamic.dk.customer.tdc.net) |
| 2021-06-04 08:03:07 | → | ddellaco_ joins (~ddellacos@89.46.62.18) |
| 2021-06-04 08:04:15 | → | Guest80 joins (~Guest80@180.168.212.6) |
| 2021-06-04 08:05:32 | × | Guest80 quits (~Guest80@180.168.212.6) (Client Quit) |
| 2021-06-04 08:05:53 | × | cfricke quits (~cfricke@user/cfricke) (Quit: WeeChat 3.1) |
| 2021-06-04 08:06:08 | <dminuoso> | beaky: Better yet, the same reason that caused the unexpected behavior is why it's very hard to catch reasonably |
| 2021-06-04 08:06:20 | <dminuoso> | (And that catching pure exception requires IO) |
| 2021-06-04 08:06:30 | <dminuoso> | And then ontop, you can't sensibly discriminate on the error |
| 2021-06-04 08:07:08 | × | imdoor quits (~imdoor@balticom-142-78-50.balticom.lv) (Quit: imdoor) |
| 2021-06-04 08:07:25 | → | fizbin joins (~fizbin@c-73-33-197-160.hsd1.nj.comcast.net) |
| 2021-06-04 08:07:35 | → | dpl_ joins (~dpl@77-121-78-163.chn.volia.net) |
| 2021-06-04 08:07:36 | × | ddellaco_ quits (~ddellacos@89.46.62.18) (Ping timeout: 244 seconds) |
| 2021-06-04 08:09:47 | → | rk04 joins (~rk04@user/rajk) |
| 2021-06-04 08:09:55 | × | dpl quits (~dpl@77-121-78-163.chn.volia.net) (Ping timeout: 245 seconds) |
| 2021-06-04 08:10:07 | <dminuoso> | Most uses of `error` are just accidents waiting to happen. :) |
| 2021-06-04 08:10:37 | Kaipi | is now known as Kaiepi |
| 2021-06-04 08:10:55 | × | hendursaga quits (~weechat@user/hendursaga) (Ping timeout: 252 seconds) |
| 2021-06-04 08:12:03 | → | imdoor joins (~imdoor@balticom-142-78-50.balticom.lv) |
| 2021-06-04 08:12:11 | × | fizbin quits (~fizbin@c-73-33-197-160.hsd1.nj.comcast.net) (Ping timeout: 272 seconds) |
| 2021-06-04 08:12:14 | <bor0> | What's a more practical way to write `combined` and `combined'`? I feel it has to do something with lifting/transformers https://paste.tomsmeding.com/i3Spjely |
| 2021-06-04 08:12:57 | <bor0> | I tried to write it using `do` notation and `lift` but couldn't get it |
| 2021-06-04 08:13:44 | <dminuoso> | bor0: First, there appear to be various subtle errors with name shadowing in your code. |
| 2021-06-04 08:13:53 | <dminuoso> | mooEg x = moo x >>= (\x -> return (x + 1)) |
| 2021-06-04 08:14:07 | <dminuoso> | Here the inner lambdas binder shadows the outer x |
All times are in UTC.