2023/02/19

2023-02-19 00:01:33 +0100telser(~quassel@user/telser) (Ping timeout: 252 seconds)
2023-02-19 00:01:39 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 00:01:39 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 00:03:38 +0100telser(~quassel@user/telser)
2023-02-19 00:05:46 +0100Tuplanolla(~Tuplanoll@91-159-68-152.elisa-laajakaista.fi) (Quit: Leaving.)
2023-02-19 00:06:31 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl) (Ping timeout: 246 seconds)
2023-02-19 00:08:40 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 00:08:40 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 00:09:49 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2023-02-19 00:10:20 +0100azimut(~azimut@gateway/tor-sasl/azimut) (Remote host closed the connection)
2023-02-19 00:10:48 +0100azimut(~azimut@gateway/tor-sasl/azimut)
2023-02-19 00:15:39 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 00:15:39 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 00:16:46 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2023-02-19 00:22:40 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 00:22:41 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 00:27:25 +0100xbarnett(~xbarnett@89.44.10.165)
2023-02-19 00:29:41 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 00:29:42 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 00:29:54 +0100oldsk00l(~znc@ec2-3-10-215-70.eu-west-2.compute.amazonaws.com) (Ping timeout: 255 seconds)
2023-02-19 00:30:04 +0100wootehfoot(~wootehfoo@user/wootehfoot) (Quit: Leaving)
2023-02-19 00:30:53 +0100dcoutts_(~duncan@86.167.90.212) (Ping timeout: 252 seconds)
2023-02-19 00:32:36 +0100AlexZenon(~alzenon@178.34.160.79) (Ping timeout: 255 seconds)
2023-02-19 00:33:48 +0100Alex_test(~al_test@178.34.160.79) (Ping timeout: 246 seconds)
2023-02-19 00:36:21 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2023-02-19 00:36:43 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 00:36:43 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 00:36:44 +0100AlexZenon(~alzenon@178.34.160.79)
2023-02-19 00:37:59 +0100FinnElija(~finn_elij@user/finn-elija/x-0085643) (Ping timeout: 255 seconds)
2023-02-19 00:38:47 +0100FinnElija(~finn_elij@user/finn-elija/x-0085643)
2023-02-19 00:39:36 +0100Alex_test(~al_test@178.34.160.79)
2023-02-19 00:42:12 +0100mechap(~mechap@user/mechap) (Quit: WeeChat 3.8)
2023-02-19 00:43:43 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 00:43:43 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 00:47:51 +0100xbarnett(~xbarnett@89.44.10.165) (Remote host closed the connection)
2023-02-19 00:49:11 +0100azimut(~azimut@gateway/tor-sasl/azimut) (Remote host closed the connection)
2023-02-19 00:49:39 +0100azimut(~azimut@gateway/tor-sasl/azimut)
2023-02-19 00:50:43 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 00:50:43 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 00:57:43 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 00:57:43 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 01:02:35 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7)
2023-02-19 01:04:45 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 01:04:45 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 01:11:45 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 01:11:45 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 01:15:07 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Ping timeout: 248 seconds)
2023-02-19 01:18:47 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 01:18:47 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 01:19:17 +0100mauke_(~mauke@user/mauke)
2023-02-19 01:20:38 +0100mauke(~mauke@user/mauke) (Ping timeout: 255 seconds)
2023-02-19 01:20:38 +0100mauke_mauke
2023-02-19 01:23:20 +0100tcard(~tcard@2400:4051:5801:7500:cf17:befc:ff82:5303) (Ping timeout: 255 seconds)
2023-02-19 01:23:24 +0100tcard_(~tcard@2400:4051:5801:7500:cf17:befc:ff82:5303)
2023-02-19 01:25:46 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 01:25:47 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 01:27:39 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7)
2023-02-19 01:27:57 +0100vglfr(~vglfr@88.155.56.103) (Ping timeout: 255 seconds)
2023-02-19 01:29:49 +0100acidjnk(~acidjnk@p200300d6e715c42481098173da91238f.dip0.t-ipconnect.de) (Ping timeout: 246 seconds)
2023-02-19 01:32:46 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 01:32:46 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 01:34:52 +0100opticblast(~Thunderbi@172.58.82.191) (Quit: opticblast)
2023-02-19 01:35:10 +0100opticblast(~Thunderbi@172.58.82.191)
2023-02-19 01:37:00 +0100opticblast(~Thunderbi@172.58.82.191) (Client Quit)
2023-02-19 01:37:21 +0100opticblast(~Thunderbi@172.58.82.191)
2023-02-19 01:39:47 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 01:39:47 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 01:44:45 +0100travisb_(~travisb@2600:1700:7990:24e0:abed:c122:a91f:97ed) (Remote host closed the connection)
2023-02-19 01:44:57 +0100travisb_(~travisb@2600:1700:7990:24e0:a63a:1f39:8aa8:be50)
2023-02-19 01:46:07 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 01:46:07 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Client Quit)
2023-02-19 01:46:23 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Ping timeout: 248 seconds)
2023-02-19 01:47:07 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 01:49:50 +0100raehik(~raehik@cpc95906-rdng25-2-0-cust156.15-3.cable.virginm.net) (Ping timeout: 268 seconds)
2023-02-19 01:51:11 +0100mikoto-chan(~mikoto-ch@2001:999:250:81ee:23c4:8735:cf7a:82c6) (Ping timeout: 252 seconds)
2023-02-19 01:53:43 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7)
2023-02-19 01:57:25 +0100gurkenglas(~gurkengla@46.114.183.40) (Ping timeout: 252 seconds)
2023-02-19 01:59:55 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Ping timeout: 246 seconds)
2023-02-19 02:02:03 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7)
2023-02-19 02:03:30 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl)
2023-02-19 02:09:22 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl) (Ping timeout: 246 seconds)
2023-02-19 02:10:42 +0100brettgilio(~brettgili@x-irc.gq) (Ping timeout: 255 seconds)
2023-02-19 02:11:00 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Remote host closed the connection)
2023-02-19 02:17:24 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 02:17:24 +0100 <albet70> my project has cabal, when I run cabal run, cabal can't find source for TelegramSendMsg in app
2023-02-19 02:21:14 +0100zaquest(~notzaques@5.130.79.72) (Remote host closed the connection)
2023-02-19 02:21:15 +0100PotentialUser-23(~Potential@2600:8800:7b00:2aa0:68f1:2f6f:21cc:c39c)
2023-02-19 02:21:42 +0100 <albet70> how using cabal to compile to a native binary program?
2023-02-19 02:22:44 +0100PotentialUser-23(~Potential@2600:8800:7b00:2aa0:68f1:2f6f:21cc:c39c) ()
2023-02-19 02:26:27 +0100wroathe(~wroathe@207-153-38-140.fttp.usinternet.com)
2023-02-19 02:26:27 +0100wroathe(~wroathe@207-153-38-140.fttp.usinternet.com) (Changing host)
2023-02-19 02:26:27 +0100wroathe(~wroathe@user/wroathe)
2023-02-19 02:52:56 +0100cassaundra(~cassaundr@c-73-25-18-25.hsd1.or.comcast.net)
2023-02-19 02:52:58 +0100kee(~~kee@user/wizzwizz4) (Read error: Connection reset by peer)
2023-02-19 02:53:02 +0100cassaundra(~cassaundr@c-73-25-18-25.hsd1.or.comcast.net) (Changing host)
2023-02-19 02:53:02 +0100cassaundra(~cassaundr@user/cassaundra)
2023-02-19 02:53:17 +0100n0den1te(~n0den1te@223.178.80.253)
2023-02-19 02:53:24 +0100jpds(~jpds@gateway/tor-sasl/jpds) (Remote host closed the connection)
2023-02-19 02:53:40 +0100kee(~~kee@user/wizzwizz4)
2023-02-19 02:54:16 +0100jpds(~jpds@gateway/tor-sasl/jpds)
2023-02-19 02:56:55 +0100dextaa0(~DV@user/dextaa)
2023-02-19 02:58:41 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection)
2023-02-19 02:59:00 +0100dextaa(~DV@user/dextaa) (Ping timeout: 260 seconds)
2023-02-19 02:59:00 +0100dextaa0dextaa
2023-02-19 03:00:14 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex)
2023-02-19 03:02:23 +0100king_gs(~Thunderbi@2806:103e:29:1779:2dd6:bac2:8268:e668)
2023-02-19 03:04:31 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Ping timeout: 252 seconds)
2023-02-19 03:17:28 +0100p0lyph3m(~polyphem@2a02:810d:840:8754:ad77:3864:324d:fcd8) (Read error: Connection reset by peer)
2023-02-19 03:37:18 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7)
2023-02-19 03:37:57 +0100raehik(~raehik@cpc95906-rdng25-2-0-cust156.15-3.cable.virginm.net)
2023-02-19 03:41:47 +0100 <zero> how do i disable default type warnings on ghci?
2023-02-19 03:42:38 +0100 <c_wraith> zero: :set -w
2023-02-19 03:42:49 +0100 <c_wraith> ok, that disables *all* warnings
2023-02-19 03:42:54 +0100 <c_wraith> but it's fast!
2023-02-19 03:43:05 +0100 <zero> lol
2023-02-19 03:43:24 +0100 <zero> i just want the opposite to :seti -Wtype-defaults
2023-02-19 03:43:42 +0100 <c_wraith> you can just negate the error type
2023-02-19 03:43:49 +0100 <c_wraith> -Wno-type-defaults
2023-02-19 03:43:56 +0100 <albet70> Could not find module ‘GHC.Int.Int64’ is it already in base?
2023-02-19 03:44:06 +0100 <zero> thanks
2023-02-19 03:44:52 +0100 <c_wraith> albet70: that looks like a type, not a modules. the module would be GHC.Int
2023-02-19 03:44:55 +0100 <albet70> oh Int64 is a type
2023-02-19 03:46:07 +0100 <albet70> how to change cabal output path for the generated binary?
2023-02-19 03:46:13 +0100 <albet70> —builddir ?
2023-02-19 03:47:27 +0100telser(~quassel@user/telser) (Ping timeout: 248 seconds)
2023-02-19 03:50:50 +0100telser(~quassel@user/telser)
2023-02-19 03:53:15 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Ping timeout: 260 seconds)
2023-02-19 03:54:55 +0100brettgilio(~brettgili@x-irc.gq)
2023-02-19 03:58:35 +0100jero98772(~jero98772@2800:484:1d80:d8ce:efcc:cbb3:7f2a:6dff) (Remote host closed the connection)
2023-02-19 04:05:59 +0100Duste3(~Duste3@46.2.23.192)
2023-02-19 04:06:06 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl)
2023-02-19 04:06:40 +0100 <Duste3> hi can someone tell me why it can't install base? http://codepad.org/DAfKZQHz
2023-02-19 04:07:00 +0100 <Duste3> it looks like there are multiple versions rejected but they are in the ranges
2023-02-19 04:08:33 +0100n0den1te(~n0den1te@223.178.80.253) ()
2023-02-19 04:09:03 +0100chexum(~quassel@gateway/tor-sasl/chexum) (Remote host closed the connection)
2023-02-19 04:09:44 +0100chexum(~quassel@gateway/tor-sasl/chexum)
2023-02-19 04:25:11 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7)
2023-02-19 04:25:27 +0100razetime(~Thunderbi@117.193.5.87)
2023-02-19 04:31:44 +0100czy(~user@host-140-23.ilcub310.champaign.il.us.clients.pavlovmedia.net)
2023-02-19 04:40:34 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl) (Ping timeout: 246 seconds)
2023-02-19 04:40:59 +0100azimut(~azimut@gateway/tor-sasl/azimut) (Ping timeout: 255 seconds)
2023-02-19 04:41:15 +0100terrorjack(~terrorjac@2a01:4f8:1c1e:4e8c::) (Quit: The Lounge - https://thelounge.chat)
2023-02-19 04:41:30 +0100 <sclv> Duste3: base isn’t reinstallalble
2023-02-19 04:41:56 +0100 <sclv> its fixed to whatever ships with ghx
2023-02-19 04:41:59 +0100 <sclv> ghc
2023-02-19 04:42:18 +0100terrorjack(~terrorjac@2a01:4f8:1c1e:4e8c::)
2023-02-19 04:43:57 +0100x_kuru(~xkuru@user/xkuru)
2023-02-19 04:44:50 +0100mikess(~sam@user/mikess)
2023-02-19 04:46:52 +0100xkuru(~xkuru@user/xkuru) (Ping timeout: 246 seconds)
2023-02-19 04:50:00 +0100td_(~td@i53870933.versanet.de) (Ping timeout: 255 seconds)
2023-02-19 04:51:46 +0100td_(~td@i5387093b.versanet.de)
2023-02-19 04:54:26 +0100[itchyjunk](~itchyjunk@user/itchyjunk/x-7353470)
2023-02-19 04:56:07 +0100FinnElija(~finn_elij@user/finn-elija/x-0085643) (Killed (NickServ (Forcing logout FinnElija -> finn_elija)))
2023-02-19 04:56:07 +0100finn_elija(~finn_elij@user/finn-elija/x-0085643)
2023-02-19 04:56:07 +0100finn_elijaFinnElija
2023-02-19 04:59:00 +0100razetime(~Thunderbi@117.193.5.87) (Ping timeout: 255 seconds)
2023-02-19 05:10:39 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Ping timeout: 252 seconds)
2023-02-19 05:16:24 +0100Quinten[m](~quintenkd@2001:470:69fc:105::3:1b1c)
2023-02-19 05:17:06 +0100opticblast(~Thunderbi@172.58.82.191) (Quit: opticblast)
2023-02-19 05:17:22 +0100opticblast(~Thunderbi@172.58.85.230)
2023-02-19 05:25:22 +0100raehik(~raehik@cpc95906-rdng25-2-0-cust156.15-3.cable.virginm.net) (Ping timeout: 246 seconds)
2023-02-19 05:29:09 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 255 seconds)
2023-02-19 05:30:05 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
2023-02-19 05:34:05 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2023-02-19 05:34:48 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Client Quit)
2023-02-19 05:43:32 +0100razetime(~Thunderbi@117.193.5.87)
2023-02-19 05:47:08 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Read error: Connection reset by peer)
2023-02-19 05:53:19 +0100[itchyjunk](~itchyjunk@user/itchyjunk/x-7353470) (Remote host closed the connection)
2023-02-19 05:56:14 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
2023-02-19 05:59:55 +0100emmanuelux_(~emmanuelu@user/emmanuelux)
2023-02-19 06:01:16 +0100 <zero> gloss doesn't do anti-alias?
2023-02-19 06:02:54 +0100_leo___(~emmanuelu@user/emmanuelux) (Ping timeout: 255 seconds)
2023-02-19 06:05:09 +0100mikoto-chan(~mikoto-ch@2001:999:250:81ee:23c4:8735:cf7a:82c6)
2023-02-19 06:13:36 +0100king_gs(~Thunderbi@2806:103e:29:1779:2dd6:bac2:8268:e668) (Ping timeout: 248 seconds)
2023-02-19 06:28:13 +0100wroathe(~wroathe@user/wroathe) (Quit: leaving)
2023-02-19 06:36:40 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl)
2023-02-19 06:39:23 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.)
2023-02-19 06:40:31 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10)
2023-02-19 06:41:36 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl) (Ping timeout: 255 seconds)
2023-02-19 06:45:02 +0100x_kuru(~xkuru@user/xkuru) (Read error: Connection reset by peer)
2023-02-19 06:51:55 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Read error: Connection reset by peer)
2023-02-19 06:54:58 +0100abhixec(~abhinav@67.169.139.16)
2023-02-19 06:59:28 +0100bitmapper(uid464869@id-464869.lymington.irccloud.com)
2023-02-19 07:03:05 +0100Duste3(~Duste3@46.2.23.192) (Remote host closed the connection)
2023-02-19 07:23:16 +0100cheater_(~Username@user/cheater)
2023-02-19 07:25:25 +0100cheater(~Username@user/cheater) (Ping timeout: 246 seconds)
2023-02-19 07:25:30 +0100cheater_cheater
2023-02-19 07:27:13 +0100falafel(~falafel@2607:fb91:143f:e47f:151f:f468:e134:97f2)
2023-02-19 07:48:33 +0100harveypwca(~harveypwc@2601:246:c180:a570:3828:d8:e523:3f67) (Quit: Leaving)
2023-02-19 07:49:16 +0100mikoto-chan(~mikoto-ch@2001:999:250:81ee:23c4:8735:cf7a:82c6) (Ping timeout: 252 seconds)
2023-02-19 07:50:26 +0100bliminse(~bliminse@user/bliminse)
2023-02-19 07:50:30 +0100bliminse(~bliminse@user/bliminse) (Client Quit)
2023-02-19 07:53:19 +0100bliminse(~bliminse@user/bliminse)
2023-02-19 07:53:47 +0100mikoto-chan(~mikoto-ch@85-76-71-143-nat.elisa-mobile.fi)
2023-02-19 07:54:50 +0100analoq(~yashi@user/dies) (Ping timeout: 255 seconds)
2023-02-19 07:55:32 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2023-02-19 07:56:06 +0100trev(~trev@user/trev)
2023-02-19 07:56:38 +0100analoq(~yashi@user/dies)
2023-02-19 07:56:51 +0100takuan(~takuan@178-116-218-225.access.telenet.be)
2023-02-19 08:00:35 +0100king_gs(~Thunderbi@187.201.41.239)
2023-02-19 08:01:15 +0100czy(~user@host-140-23.ilcub310.champaign.il.us.clients.pavlovmedia.net) (Ping timeout: 255 seconds)
2023-02-19 08:06:05 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2023-02-19 08:13:10 +0100farzad(~farzad@83.121.6.134)
2023-02-19 08:19:29 +0100 <farzad> Hi! Anyone know of an equivalent of haskells polysemy for purescript?
2023-02-19 08:27:49 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2023-02-19 08:28:10 +0100cheater_(~Username@user/cheater)
2023-02-19 08:29:36 +0100king_gs(~Thunderbi@187.201.41.239) (Ping timeout: 255 seconds)
2023-02-19 08:30:10 +0100cheater(~Username@user/cheater) (Ping timeout: 246 seconds)
2023-02-19 08:30:15 +0100cheater_cheater
2023-02-19 08:33:13 +0100king_gs(~Thunderbi@187.201.41.239)
2023-02-19 08:37:12 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl)
2023-02-19 08:42:38 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 255 seconds)
2023-02-19 08:44:19 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex)
2023-02-19 08:46:37 +0100machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net) (Ping timeout: 246 seconds)
2023-02-19 08:49:53 +0100inversed(~inversed@bcdcac82.skybroadband.com)
2023-02-19 09:07:24 +0100mikoto-chan(~mikoto-ch@85-76-71-143-nat.elisa-mobile.fi) (Ping timeout: 255 seconds)
2023-02-19 09:10:40 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl) (Ping timeout: 252 seconds)
2023-02-19 09:16:08 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:c515:5d78:dd35:61fc) (Remote host closed the connection)
2023-02-19 09:17:18 +0100razetime(~Thunderbi@117.193.5.87) (Ping timeout: 255 seconds)
2023-02-19 09:20:47 +0100ddellacosta(~ddellacos@146.70.166.221) (Ping timeout: 255 seconds)
2023-02-19 09:25:38 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Read error: Connection reset by peer)
2023-02-19 09:30:51 +0100razetime(~Thunderbi@117.193.5.87)
2023-02-19 09:32:27 +0100king_gs(~Thunderbi@187.201.41.239) (Quit: king_gs)
2023-02-19 09:35:47 +0100Lycurgus(~juan@user/Lycurgus)
2023-02-19 09:41:28 +0100mauke(~mauke@user/mauke) (Quit: leaving)
2023-02-19 09:42:47 +0100meinside(uid24933@id-24933.helmsley.irccloud.com) (Quit: Connection closed for inactivity)
2023-02-19 09:44:11 +0100mikess(~sam@user/mikess) (Ping timeout: 252 seconds)
2023-02-19 09:45:49 +0100mauke(~mauke@user/mauke)
2023-02-19 09:46:28 +0100opticblast(~Thunderbi@172.58.85.230) (Ping timeout: 246 seconds)
2023-02-19 09:46:43 +0100gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c)
2023-02-19 09:48:14 +0100L29Ah(~L29Ah@wikipedia/L29Ah) (Ping timeout: 255 seconds)
2023-02-19 09:50:29 +0100oldsk00l(~znc@ec2-18-134-205-208.eu-west-2.compute.amazonaws.com)
2023-02-19 09:51:49 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl)
2023-02-19 09:52:16 +0100acidjnk(~acidjnk@p200300d6e715c480d175a2749fc75020.dip0.t-ipconnect.de)
2023-02-19 09:52:47 +0100falafel(~falafel@2607:fb91:143f:e47f:151f:f468:e134:97f2) (Ping timeout: 248 seconds)
2023-02-19 09:54:56 +0100mauke(~mauke@user/mauke) (Read error: Connection reset by peer)
2023-02-19 09:55:37 +0100mauke(~mauke@user/mauke)
2023-02-19 10:02:15 +0100jpds(~jpds@gateway/tor-sasl/jpds) (Remote host closed the connection)
2023-02-19 10:03:02 +0100jpds(~jpds@gateway/tor-sasl/jpds)
2023-02-19 10:04:27 +0100andrewboltachev(~andrey@178.141.125.176)
2023-02-19 10:07:43 +0100farzad(~farzad@83.121.6.134) (Ping timeout: 248 seconds)
2023-02-19 10:13:46 +0100oldsk00l(~znc@ec2-18-134-205-208.eu-west-2.compute.amazonaws.com) (Ping timeout: 246 seconds)
2023-02-19 10:16:05 +0100gmg(~user@user/gehmehgeh) (Remote host closed the connection)
2023-02-19 10:16:36 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:bc09:17b4:a9c9:5fe5)
2023-02-19 10:17:50 +0100gmg(~user@user/gehmehgeh)
2023-02-19 10:18:19 +0100justsomeguy(~justsomeg@user/justsomeguy) (Ping timeout: 246 seconds)
2023-02-19 10:19:23 +0100abhixec(~abhinav@67.169.139.16) (Ping timeout: 252 seconds)
2023-02-19 10:20:51 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:bc09:17b4:a9c9:5fe5) (Ping timeout: 252 seconds)
2023-02-19 10:28:11 +0100Lycurgus(~juan@user/Lycurgus) (Quit: Exeunt: personae.ai-integration.biz)
2023-02-19 10:36:47 +0100bitmapper(uid464869@id-464869.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2023-02-19 10:47:22 +0100freeside(~mengwong@103.252.202.170) (Ping timeout: 246 seconds)
2023-02-19 10:51:43 +0100gurkenglas(~gurkengla@dynamic-046-114-183-040.46.114.pool.telefonica.de)
2023-02-19 10:54:57 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl) (Ping timeout: 255 seconds)
2023-02-19 11:03:24 +0100razetime1(~Thunderbi@117.193.2.252)
2023-02-19 11:03:49 +0100razetime(~Thunderbi@117.193.5.87) (Ping timeout: 246 seconds)
2023-02-19 11:07:40 +0100razetime1(~Thunderbi@117.193.2.252) (Ping timeout: 246 seconds)
2023-02-19 11:08:49 +0100razetime(~Thunderbi@117.193.3.43)
2023-02-19 11:14:34 +0100farzad(~farzad@192.15.7.16)
2023-02-19 11:15:25 +0100farzad(~farzad@192.15.7.16) (Client Quit)
2023-02-19 11:18:29 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:50e2:6d7:efc7:59a5)
2023-02-19 11:43:06 +0100Mahi(~Mahi@91-159-147-164.elisa-laajakaista.fi)
2023-02-19 11:44:23 +0100tzh(~tzh@c-24-21-73-154.hsd1.wa.comcast.net) (Quit: zzz)
2023-02-19 11:44:26 +0100 <Mahi> Hello, my task's instructions tell me to use this function: https://paste.tomsmeding.com/PjMMDUtN and tell me to modify the "events" list with new events added inside the function - but everything I google says I can't modify lists? Any ideas?
2023-02-19 11:47:36 +0100 <[exa]> Mahi: well technically you can't modify anything because of purity
2023-02-19 11:47:47 +0100 <Mahi> I've already written a function that returns a new function with the added event: `addEvent name place date events = ((EventInfo name place date) : events)` but I don't understand how to use this inside the provided IO function
2023-02-19 11:47:54 +0100 <Mahi> returns a new list*
2023-02-19 11:48:07 +0100 <[exa]> but commonly "modifying" means basically making a copy of the list with the stuff replaced where you wanted the changes
2023-02-19 11:48:40 +0100 <Mahi> yes so I'd like to replace the existing `events` variable with my new data, is that possible?
2023-02-19 11:49:00 +0100 <[exa]> yeah
2023-02-19 11:49:30 +0100 <[exa]> I'm still a bit confused about what the function should do, the `loop` is an IO action that continues the processing and returns (), right?
2023-02-19 11:50:00 +0100 <[exa]> and you basically want to enrich the list a bit with a few new events every here and there so that loop does something else?
2023-02-19 11:50:04 +0100 <Mahi> https://paste.tomsmeding.com/UB3vijwd
2023-02-19 11:50:22 +0100 <Mahi> yes the loop takes an input string until "Quit" is written
2023-02-19 11:50:29 +0100 <Mahi> And my job is to keep modifying the list based on the input
2023-02-19 11:51:29 +0100Tuplanolla(~Tuplanoll@91-159-68-152.elisa-laajakaista.fi)
2023-02-19 11:51:30 +0100 <[exa]> I kinda fail to see what's the reason to have it wrapped in "IO" but let's leave that for later I guess :D
2023-02-19 11:51:52 +0100 <Mahi> I'm wondering if the original function provided by teachers should instead be this: https://paste.tomsmeding.com/uccc4zDh
2023-02-19 11:52:19 +0100 <Mahi> the original one they provided makes it seem liek I should edit the `events` variable instead of returning a new list?
2023-02-19 11:52:22 +0100 <[exa]> yeah but that doesn't leave you an opportunity to do an IO action (such as printing a response to the command)
2023-02-19 11:52:27 +0100 <Mahi> ahh
2023-02-19 11:52:43 +0100 <Mahi> that explains
2023-02-19 11:52:55 +0100 <[exa]> anyway, do you have an example of an action that you want to run with 1] what it does 2] what id adds to the event list?
2023-02-19 11:53:45 +0100 <Mahi> Input: Event 'Some Event X' happens at 'Some Place Y' on '2019-10-08' should print "Event added" and add the event
2023-02-19 11:53:50 +0100 <[exa]> btw modifying the list is done basically with making a new one, e.g. for prepending you do basically: loop $ return (myEvent : events)
2023-02-19 11:54:14 +0100 <Mahi> yeah that's what threw me off the most, now that you've said it it's obvious :D
2023-02-19 11:54:58 +0100 <[exa]> I still don't really see the reason to have the eventlist wrapped in IO, but I guess that's gonna explain itself with more actions
2023-02-19 11:55:03 +0100econo(uid147250@user/econo) (Quit: Connection closed for inactivity)
2023-02-19 11:56:08 +0100 <Mahi> The only other actions are all like this, Input: "What happens on '2019-10-08'" => prints a list of events
2023-02-19 11:56:28 +0100 <Mahi> similarly "What happens at <place>" and "What is <eventname>"
2023-02-19 11:56:34 +0100 <Mahi> that's all there is to the task
2023-02-19 11:57:23 +0100 <[exa]> anyway at this point I'd go: ...; events <- ioEvents; newEvents <- case parseEvent of {.....} ; loop $ return (newEvents ++ events)
2023-02-19 11:57:46 +0100 <[exa]> errr... parseCommand. :]
2023-02-19 11:58:26 +0100 <[exa]> or so, schematically
2023-02-19 11:58:28 +0100 <Mahi> I was trying to use `do` somehow
2023-02-19 11:58:44 +0100 <[exa]> you actually need to have access to the event list in order to execute the command
2023-02-19 11:59:22 +0100 <[exa]> `do` is for gluing IO actions together (and also of other monadic actions that are of no interest right now)
2023-02-19 12:01:52 +0100 <Mahi> Thanks for the help, I think I need to watch a youtube guide on IO or something, everything else in the task seems simple to me but the printing and reading input
2023-02-19 12:02:37 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 246 seconds)
2023-02-19 12:02:38 +0100 <Mahi> I just can't understand how to do imperative stuff in functional programming :D "print something and return something else entirely" seems imposible
2023-02-19 12:04:22 +0100 <[exa]> Mahi: it's a bit confusing but there are pretty good rule of thumbs on how to do this
2023-02-19 12:04:35 +0100azimut(~azimut@gateway/tor-sasl/azimut)
2023-02-19 12:04:51 +0100razetime(~Thunderbi@117.193.3.43) (Remote host closed the connection)
2023-02-19 12:05:56 +0100 <[exa]> in summary, by types: `something` is a plain value that you can access and play with it`. `IO something` is a program that produces the plain value if you run it. Because of purity, you can't run side-effect-causing programs anywhere, the only way to run them is to do it within a larger IO program and let the system to glue the side-effects together to form a larger IO program.
2023-02-19 12:05:59 +0100the_proffesor(~theproffe@2601:282:8880:20:cbd6:9442:3ec7:7047)
2023-02-19 12:05:59 +0100the_proffesor(~theproffe@2601:282:8880:20:cbd6:9442:3ec7:7047) (Changing host)
2023-02-19 12:05:59 +0100the_proffesor(~theproffe@user/theproffesor)
2023-02-19 12:06:44 +0100 <[exa]> Mahi: `do` notation is exactly the thing that does this gluing, if you write `do program1; program2` it just makes a program that runs both the subprograms in sequence.
2023-02-19 12:07:36 +0100 <Mahi> So why can't I do something like `events <- if blabla then do { print "something"; return someEvents  }`
2023-02-19 12:07:54 +0100 <[exa]> Mahi: and to extract the results of programs, you use the <- (or "bind") notation. `do val<-program1; program2 val` constructs a IO program that runs program 1 and feeds its output directly to program2
2023-02-19 12:08:18 +0100 <[exa]> btw internally these are rewritten to >> and >>=, you may want to examine the types in ghci using say :t (>>)
2023-02-19 12:09:21 +0100 <[exa]> and the only remaining part is return, which constructs a "trivial program" that doesn't really do anything but produces the value that you give it; which is useful for gluing your computation results into the IO programs
2023-02-19 12:09:58 +0100theproffesor(~theproffe@user/theproffesor) (Ping timeout: 246 seconds)
2023-02-19 12:10:06 +0100 <[exa]> in short: `<-` allows you to go from `IO something` (on the right) to `something` (on the left), `return` does the reverse, and everything you put into `do` must be an `IO whatever` program
2023-02-19 12:10:40 +0100 <[exa]> s/put into/run in/ -- probably a better wording
2023-02-19 12:11:08 +0100 <Mahi> Hmm thank you very much
2023-02-19 12:11:11 +0100 <[exa]> the code you pasted will probably be rejected by a typechecker
2023-02-19 12:11:28 +0100acidjnk(~acidjnk@p200300d6e715c480d175a2749fc75020.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2023-02-19 12:11:50 +0100 <[exa]> `print "something" :: IO ()` (program that returns an "empty" value), but `return someEvents :: IO [EventInfo]`
2023-02-19 12:12:27 +0100 <[exa]> in turn, if you would do `events <- ....`; it wouldn't know if events should be () or [EventInfo]
2023-02-19 12:13:30 +0100 <[exa]> btw there are various ways to circumvent that, for example you can do `do print "something"; return []` which is a IO program that prints what you want and still returns a type-compatible list
2023-02-19 12:13:53 +0100 <[exa]> (equivalent notation: print "something" >> return [] )
2023-02-19 12:14:02 +0100 <[exa]> (without `do` ^)
2023-02-19 12:14:22 +0100szkl(uid110435@id-110435.uxbridge.irccloud.com)
2023-02-19 12:15:22 +0100 <Mahi> hmm yes yes, I'm starting to get a hang of it :D thank you for the help
2023-02-19 12:16:03 +0100 <[exa]> it takes some practice but becomes pretty intuitive later
2023-02-19 12:16:10 +0100 <Mahi> let's hope so
2023-02-19 12:17:24 +0100 <[exa]> btw many people tend to think that the IO actually "runs" a side effect; that's a practical but slightly misleading view. In fact you're building a description of a huge `main :: IO ()` program that the haskell runtime then later interprets
2023-02-19 12:21:47 +0100Mahi(~Mahi@91-159-147-164.elisa-laajakaista.fi) (Quit: Client closed)
2023-02-19 12:22:46 +0100Sgeo(~Sgeo@user/sgeo) (Read error: Connection reset by peer)
2023-02-19 12:33:14 +0100bgs(~bgs@212-85-160-171.dynamic.telemach.net)
2023-02-19 12:36:32 +0100jmdaemon(~jmdaemon@user/jmdaemon) (Ping timeout: 248 seconds)
2023-02-19 12:41:03 +0100gawen(~gawen@user/gawen) (Quit: cya)
2023-02-19 12:47:23 +0100gawen(~gawen@user/gawen)
2023-02-19 12:51:34 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl)
2023-02-19 13:02:03 +0100CiaoSen(~Jura@p200300c9570460002a3a4dfffe84dbd5.dip0.t-ipconnect.de)
2023-02-19 13:06:05 +0100saolsen(sid26430@id-26430.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2023-02-19 13:11:22 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) (Quit: = "")
2023-02-19 13:15:40 +0100wootehfoot(~wootehfoo@user/wootehfoot)
2023-02-19 13:15:41 +0100FinnElija(~finn_elij@user/finn-elija/x-0085643) (Remote host closed the connection)
2023-02-19 13:16:28 +0100cassaundra(~cassaundr@user/cassaundra) (Ping timeout: 246 seconds)
2023-02-19 13:16:34 +0100FinnElija(~finn_elij@user/finn-elija/x-0085643)
2023-02-19 13:26:40 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl) (Ping timeout: 268 seconds)
2023-02-19 13:34:41 +0100azimut(~azimut@gateway/tor-sasl/azimut) (Ping timeout: 255 seconds)
2023-02-19 13:35:33 +0100azimut(~azimut@gateway/tor-sasl/azimut)
2023-02-19 13:36:13 +0100jpds(~jpds@gateway/tor-sasl/jpds) (Remote host closed the connection)
2023-02-19 13:37:02 +0100jpds(~jpds@gateway/tor-sasl/jpds)
2023-02-19 13:54:12 +0100gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c) (Quit: WeeChat 3.8)
2023-02-19 13:56:49 +0100califax(~califax@user/califx) (Remote host closed the connection)
2023-02-19 13:57:40 +0100califax(~califax@user/califx)
2023-02-19 14:03:43 +0100sagax(~sagax_nb@user/sagax) (Quit: Konversation terminated!)
2023-02-19 14:10:41 +0100jrm(~jrm@user/jrm) (Remote host closed the connection)
2023-02-19 14:11:18 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Remote host closed the connection)
2023-02-19 14:11:43 +0100jrm(~jrm@user/jrm)
2023-02-19 14:11:43 +0100jrm(~jrm@user/jrm) (Client Quit)
2023-02-19 14:12:32 +0100 <bramhaag> I'm trying to parse a String that can only contain alphanumeric characters, -, and _ using megaparsec. The first and last character should not be a - or _, and the string has to be at least 1 character long. I expressed it as the following regular expression: [a-zA-Z0-9]+ ([_-]+ [a-zA-Z0-9]+)*. Directly translating this regex to megaparsec gives me
2023-02-19 14:12:32 +0100 <bramhaag> a rather ugly parser, an attempt to reduce the amount of many and some calls also did not make it more readable (https://paste.tomsmeding.com/jGFf05nu). Is there an easier way to define this?
2023-02-19 14:13:00 +0100jrm(~jrm@user/jrm)
2023-02-19 14:13:23 +0100gmg(~user@user/gehmehgeh) (Ping timeout: 255 seconds)
2023-02-19 14:16:37 +0100jrm(~jrm@user/jrm) (Client Quit)
2023-02-19 14:17:25 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-02-19 14:17:56 +0100jrm(~jrm@user/jrm)
2023-02-19 14:23:35 +0100meinside(uid24933@id-24933.helmsley.irccloud.com)
2023-02-19 14:25:23 +0100shinjipf(~shinjipf@2a01:4f8:1c1c:c1be::1) (Quit: Shinji leaves)
2023-02-19 14:26:08 +0100shinjipf(~shinjipf@2a01:4f8:1c1c:c1be::1)
2023-02-19 14:28:55 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2023-02-19 14:30:37 +0100 <int-e> Something like this maybe: (:) <$> alphaNumChar <*> ((++) <$> many (oneOf "-_" <|> alphaNumChar) <*> (:[]) <$> alphaNumChar <|> pure [])
2023-02-19 14:31:05 +0100gmg(~user@user/gehmehgeh)
2023-02-19 14:31:07 +0100random-jellyfish(~random-je@user/random-jellyfish)
2023-02-19 14:31:42 +0100 <int-e> so [a-zA-Z0-9]([a-zA-Z0-9_-]*[a-zA-Z0-9])?
2023-02-19 14:32:04 +0100tomboy65(~tomboy64@user/tomboy64) (Ping timeout: 246 seconds)
2023-02-19 14:33:10 +0100tomboy64(~tomboy64@user/tomboy64)
2023-02-19 14:36:56 +0100pavonia(~user@user/siracusa) (Quit: Bye!)
2023-02-19 14:37:17 +0100 <bramhaag> Hmm, possible but imo not more readable than the others
2023-02-19 14:38:16 +0100 <int-e> it's just a tad shorter
2023-02-19 14:46:49 +0100L29Ah(~L29Ah@wikipedia/L29Ah)
2023-02-19 14:50:44 +0100califax(~califax@user/califx) (Ping timeout: 255 seconds)
2023-02-19 14:51:29 +0100califax(~califax@user/califx)
2023-02-19 14:59:35 +0100oxide(~lambda@user/oxide)
2023-02-19 15:19:44 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2023-02-19 15:21:10 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2023-02-19 15:21:17 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:bc09:17b4:a9c9:5fe5)
2023-02-19 15:21:45 +0100 <sayola> what do you think about using exceptions instead of ExceptT in a monad stack, when there is MonadIO on it already?
2023-02-19 15:22:08 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl)
2023-02-19 15:25:36 +0100 <geekosaur> exceptions are genrally a pain if they happen in pure code even if there is an IO "nearby"; ExceptT is much easier and more reliable
2023-02-19 15:25:44 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:bc09:17b4:a9c9:5fe5) (Ping timeout: 255 seconds)
2023-02-19 15:26:11 +0100 <geekosaur> if you are actually in IO when it happens, you can catch it fine, but even there I tend to prefer ExceptT
2023-02-19 15:27:59 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl) (Ping timeout: 255 seconds)
2023-02-19 15:28:20 +0100 <tomsmeding> unlike in Java, nothing stops you from forgetting to handle an IO exception
2023-02-19 15:33:04 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2023-02-19 15:41:41 +0100 <[exa]> probably depends on what you want to do with the exception though
2023-02-19 15:42:08 +0100 <[exa]> if the action is "apologize in human language and quit immediately", I'd say IO exceptions are perfectly okay
2023-02-19 15:48:15 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2023-02-19 15:49:32 +0100 <sayola> i've read that since you already have to deal with exceptions when there is IO, you might as well stick to it. ExceptT would be redundant / only add to complexity.
2023-02-19 15:50:45 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:50e2:6d7:efc7:59a5) (Remote host closed the connection)
2023-02-19 15:51:04 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:50e2:6d7:efc7:59a5)
2023-02-19 15:52:57 +0100segfaultfizzbuzz(~segfaultf@108.211.201.53)
2023-02-19 15:53:40 +0100 <segfaultfizzbuzz> i would like to talk about the concept of a "graded language" and whether or not it is impossible:
2023-02-19 15:54:35 +0100 <segfaultfizzbuzz> the simplest example of grading (in the sense of gradation) in a language i can think of is "unsafe" in rust, where some part of the code deviates from normally enforced program invariants
2023-02-19 15:56:11 +0100 <segfaultfizzbuzz> it seems like an "ideal language" would have the most strict collection of program invariants enforced throughout the codebase by default, and then on an as-needed basis different sections of code would selectively exempt themselves from those invariants
2023-02-19 15:56:42 +0100 <segfaultfizzbuzz> for a variety of reasons,... perhaps the programmer doesn't have time to prove something, perhaps some kind of performance optimization is necessary, and soforth
2023-02-19 15:57:03 +0100freeside(~mengwong@103.252.202.170)
2023-02-19 15:57:57 +0100 <hellwolf[m]> what's the concrete problem and its example to illustrate its application, say in Haskell?
2023-02-19 15:58:34 +0100 <segfaultfizzbuzz> for example it is "more strict" to enforce program totality by default, and then to have specific sections of code which are not total
2023-02-19 15:59:26 +0100 <segfaultfizzbuzz> alternatively maybe it isn't possible to do this,... but i think even that would be interesting because it would show that you can't "unify" languages,
2023-02-19 15:59:36 +0100jero98772(~jero98772@2800:484:1d80:d8ce:efcc:cbb3:7f2a:6dff)
2023-02-19 16:00:08 +0100 <segfaultfizzbuzz> the overall thrust of what i am thinking is that it is silly how many programming **languages** there are, when really what we want to do is turn on and off program invariants
2023-02-19 16:00:55 +0100 <segfaultfizzbuzz> hellwolf[m]: did i answer your question...?
2023-02-19 16:01:03 +0100 <mauke> you think that is what programming languages are about?
2023-02-19 16:01:20 +0100 <segfaultfizzbuzz> maybe? or you can improve my understanding
2023-02-19 16:02:51 +0100 <geekosaur> lotsof languages are turing complete and therefore can do the same things. the question is what things they make easy
2023-02-19 16:03:23 +0100Rembanewaves the BF-flag enthusiastically
2023-02-19 16:03:50 +0100 <hellwolf[m]> segfaultfizzbuzz: not sure. "the next 700 programming languages" came to my mind though.
2023-02-19 16:04:41 +0100acidjnk(~acidjnk@p200300d6e715c48085d724d6bf6f6012.dip0.t-ipconnect.de)
2023-02-19 16:04:41 +0100 <hellwolf[m]> Agda says it's not turing complete, since there is "silly programs" you can't write in it, so to speak loosely.
2023-02-19 16:05:49 +0100 <segfaultfizzbuzz> turing completeness defeats program invariants?
2023-02-19 16:07:22 +0100gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c)
2023-02-19 16:07:42 +0100 <segfaultfizzbuzz> put another way, what is a programming language *aside from* invariants?
2023-02-19 16:08:22 +0100 <segfaultfizzbuzz> there are "superficial" characteristics such as syntax and community, and then there are "less superficial" things such as library, but i would argue that these aren't the language itself
2023-02-19 16:08:23 +0100 <hellwolf[m]> https://math.stackexchange.com/questions/2026006/is-there-a-version-of-turing-completeness-for-tot…
2023-02-19 16:09:02 +0100 <segfaultfizzbuzz> i would say don't pay *too* much attention to totality as that was one example of a program invariant
2023-02-19 16:09:10 +0100 <hellwolf[m]> not sure do you have a clear definition od "invariants" here, wouldn't be able to discuss without one.
2023-02-19 16:10:06 +0100 <segfaultfizzbuzz> hellwolf[m]: a program invariant would be a guarantee about the program which is enforced either by the compiler or by the runtime, if there is a runtime
2023-02-19 16:10:34 +0100 <segfaultfizzbuzz> "bounds checking" for example would be a way of enforcing the program invariant that an array access doesn't go out of bounds
2023-02-19 16:11:39 +0100 <Rembane> Could a horrible crash count as enforcement of an invariant?
2023-02-19 16:15:07 +0100 <segfaultfizzbuzz> so long as the behavior is guaranteed and known, whatever that might be, then that would count as a program invariant
2023-02-19 16:15:29 +0100raehik(~raehik@cpc95906-rdng25-2-0-cust156.15-3.cable.virginm.net)
2023-02-19 16:15:39 +0100 <segfaultfizzbuzz> C as a language can be good (or better) for enforcing timing-related program invariants
2023-02-19 16:16:02 +0100 <segfaultfizzbuzz> but otherwise does not enforce much at all about the program itself
2023-02-19 16:16:47 +0100 <segfaultfizzbuzz> a programming language "exists" if one *must* make a choice between a pair of program invariants
2023-02-19 16:16:51 +0100 <mauke> C without a library is not turing complete, so that's fun
2023-02-19 16:18:12 +0100 <Quinten[m]> mauke: wait why, because you cannot allocate infinite amounts of memory?
2023-02-19 16:18:19 +0100 <hellwolf[m]> what's the simplest program to illustrate your point?
2023-02-19 16:18:32 +0100 <segfaultfizzbuzz> hellwolf[m]: are you talking to me?
2023-02-19 16:18:44 +0100 <mauke> Quinten[m]: yes
2023-02-19 16:19:07 +0100 <Quinten[m]> because if it's about memory, C99 VLA's should be able to fix that and I think those are part of the language?
2023-02-19 16:19:29 +0100 <hellwolf[m]> yes, segfaultfizzbuzz:
2023-02-19 16:19:58 +0100 <mauke> Quinten[m]: no, array elements must be addressable and your addresses are bounded by sizeof (void *)
2023-02-19 16:22:08 +0100 <Quinten[m]> okay but ultimately every computer has such limits, C with the standard library enabled also has a limited address space and so does x86_64 assembly and Haskell is affected by that too
2023-02-19 16:22:52 +0100 <mauke> Haskell isn't built out of pointers
2023-02-19 16:23:19 +0100 <mauke> C with the standard library has FILE * and fseek. you can build an infinite tape out of that
2023-02-19 16:23:23 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.)
2023-02-19 16:24:41 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10)
2023-02-19 16:25:08 +0100 <segfaultfizzbuzz> hellwolf[m]: this is probably the simplest example: https://doc.rust-lang.org/rust-by-example/unsafe/asm.html
2023-02-19 16:25:13 +0100segfaultfizzbuzz(~segfaultf@108.211.201.53) (Remote host closed the connection)
2023-02-19 16:25:55 +0100segfaultfizzbuzz(~segfaultf@108.211.201.53)
2023-02-19 16:25:58 +0100 <segfaultfizzbuzz> hellwolf[m]: this is probably the simplest example: https://doc.rust-lang.org/rust-by-example/unsafe/asm.html
2023-02-19 16:29:40 +0100 <hellwolf[m]> I guess that's what it takes to work with oily machines at times. It seems quite alright under "IO a" type. I guess I am missing what do we want to discuss here.
2023-02-19 16:33:22 +0100meinside(uid24933@id-24933.helmsley.irccloud.com) (Quit: Connection closed for inactivity)
2023-02-19 16:37:48 +0100random-jellyfish(~random-je@user/random-jellyfish) (Quit: Client closed)
2023-02-19 16:37:49 +0100segfaultfizzbuzz(~segfaultf@108.211.201.53) (Ping timeout: 252 seconds)
2023-02-19 16:38:13 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2023-02-19 16:39:01 +0100ddellacosta(~ddellacos@146.70.166.10)
2023-02-19 16:39:40 +0100kilolympus(~kilolympu@213.144.144.24)
2023-02-19 16:46:34 +0100segfaultfizzbuzz(~segfaultf@108.211.201.53)
2023-02-19 16:52:14 +0100razetime(~Thunderbi@117.193.3.43)
2023-02-19 16:53:13 +0100[itchyjunk](~itchyjunk@user/itchyjunk/x-7353470)
2023-02-19 16:53:19 +0100Axma23822(~Axman6@user/axman6)
2023-02-19 16:55:31 +0100Axman6(~Axman6@user/axman6) (Ping timeout: 268 seconds)
2023-02-19 16:56:51 +0100xff0x(~xff0x@2405:6580:b080:900:1ef3:42f8:594a:9997) (Ping timeout: 252 seconds)
2023-02-19 17:00:04 +0100wildsebastian(~wildsebas@2001:470:69fc:105::1:14b1) (Quit: You have been kicked for being idle)
2023-02-19 17:05:52 +0100merijn(~merijn@145.90.225.10)
2023-02-19 17:06:02 +0100__monty__(~toonn@user/toonn)
2023-02-19 17:21:47 +0100mikess(~sam@user/mikess)
2023-02-19 17:22:53 +0100tzh(~tzh@c-24-21-73-154.hsd1.wa.comcast.net)
2023-02-19 17:30:49 +0100eggplantade(~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net)
2023-02-19 17:34:15 +0100merijn(~merijn@145.90.225.10) (Ping timeout: 252 seconds)
2023-02-19 17:51:12 +0100CiaoSen(~Jura@p200300c9570460002a3a4dfffe84dbd5.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2023-02-19 17:51:38 +0100 <segfaultfizzbuzz> is there an intelligible/meaningful language which is more "minimal" in its enforcement of program invariants than lisp?
2023-02-19 17:51:45 +0100 <segfaultfizzbuzz> haskell is "stronger" because it has a type system
2023-02-19 17:52:23 +0100 <segfaultfizzbuzz> that is to say, lisp is just an AST and then operations on that AST, and i guess that's the "least" there is to a language?
2023-02-19 17:52:37 +0100 <tomsmeding> assembly?
2023-02-19 17:53:00 +0100 <tomsmeding> not a more minimal language, but surely more minimal in its _enforcement_ of anything
2023-02-19 17:54:25 +0100wroathe(~wroathe@user/wroathe)
2023-02-19 17:54:41 +0100 <segfaultfizzbuzz> hmm, interesting point, although
2023-02-19 17:54:55 +0100acidjnk(~acidjnk@p200300d6e715c48085d724d6bf6f6012.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2023-02-19 17:55:30 +0100 <segfaultfizzbuzz> i think (?) lisp can (probably?) be "extended" to include program invariants (eg a type system) whereas with assembly,... i don't think you can do that...?
2023-02-19 17:56:05 +0100 <tomsmeding> well "can" is a bit strong, but it wouldn't be practical
2023-02-19 17:56:35 +0100 <segfaultfizzbuzz> wait you mean i can't add types to lisp?
2023-02-19 17:57:05 +0100 <c_wraith> You can add types to the fragment you write. You can't add types to everything you depend on.
2023-02-19 17:57:33 +0100 <geekosaur> didn't Knuth have a typed assembly language?
2023-02-19 17:57:33 +0100 <c_wraith> the best you can do is add types at the edges of your dependencies.
2023-02-19 17:57:35 +0100 <tomsmeding> segfaultfizzbuzz: no I was talking about assembly
2023-02-19 17:57:48 +0100 <c_wraith> geekosaur: there's also ATS
2023-02-19 17:57:51 +0100 <segfaultfizzbuzz> tomsmeding: ah yeah, adding types to assembly would be awfully difficult
2023-02-19 17:57:52 +0100 <tomsmeding> what are you going to do with memory
2023-02-19 17:57:55 +0100kadobanana(~mud@user/kadoban) (Ping timeout: 260 seconds)
2023-02-19 17:58:23 +0100 <geekosaur> and back in the day there were limited "types" enforced via tag bits in memory
2023-02-19 17:58:35 +0100 <tomsmeding> that's dynamic though
2023-02-19 17:58:55 +0100 <tomsmeding> a dynamic type system is also a "type system", but generally when people talk about a "type system" they mean a static one :p
2023-02-19 17:59:09 +0100 <tomsmeding> "well-typed programs don't go wrong"
2023-02-19 17:59:14 +0100kadobanana(~mud@user/kadoban)
2023-02-19 17:59:27 +0100 <geekosaur> yes. and the fact that no such processors exist these days indicates that they don't work very well in practice
2023-02-19 17:59:51 +0100 <c_wraith> hmm. CHERI kind of is a type system for pointers.
2023-02-19 17:59:56 +0100 <c_wraith> And some of those processors exist
2023-02-19 18:00:25 +0100 <c_wraith> I mean, I guess it is tagging.
2023-02-19 18:00:34 +0100 <c_wraith> But it does exist in the real world, at least
2023-02-19 18:00:54 +0100 <segfaultfizzbuzz> the runtime or hardware implementation of the program invariants, from my mindset, is kind of an afterthought
2023-02-19 18:01:52 +0100 <segfaultfizzbuzz> i was meaning that assembly itself is unfriendly to "extended annotations",... there isn't really an "assembly AST" i don't think,... although that is admittedly a superficial presentation of code consideration
2023-02-19 18:02:55 +0100 <tomsmeding> it's more that in assembly you only have a limited number of "local variables", so any interesting program is going to need to use memory
2023-02-19 18:03:18 +0100 <segfaultfizzbuzz> ah yeah there is no convenient uh, symbol list? what would it be called
2023-02-19 18:03:19 +0100 <tomsmeding> C puts a static type system on memory accesses using pointers, but things become difficult when you don't even have enough local variables to store your pointers
2023-02-19 18:04:09 +0100 <tomsmeding> you can do it though (some statically-known "entry point" pointers, pointing to a struct with some known-type pointers from which your memory space spawns)
2023-02-19 18:04:37 +0100 <tomsmeding> but that would necessitate a very particular way of writing assembly, basically all existing code would not "type-check" with such a system
2023-02-19 18:07:03 +0100 <segfaultfizzbuzz> i suppose another question would be the tendency of program invariants or their violation to propagate or not propagate throughout the codebase,...
2023-02-19 18:10:03 +0100 <segfaultfizzbuzz> so people write science fiction fantasizing about flying cars and space travel and soforth, is there any science fiction written for programming languages?
2023-02-19 18:10:24 +0100 <segfaultfizzbuzz> that is to say, for "programming language scifi" people would fantasize about how they would like to express programs
2023-02-19 18:10:30 +0100wroathe(~wroathe@user/wroathe) (Quit: Lost terminal)
2023-02-19 18:10:48 +0100 <segfaultfizzbuzz> without concern for the difficulty of making a compiler/runtime meet that fantasy
2023-02-19 18:11:27 +0100 <c_wraith> segfaultfizzbuzz: Hah. I can think of one example... Tim Sweeney about 10 years ago. Funnily enough, SPJ is now working on actually implementing that language.
2023-02-19 18:12:00 +0100wroathe(~wroathe@user/wroathe)
2023-02-19 18:12:38 +0100 <segfaultfizzbuzz> yeah so maybe this is a useful way of thinking. can you link?
2023-02-19 18:13:12 +0100 <segfaultfizzbuzz> i mean link to the ten year old sweney fantasy
2023-02-19 18:13:17 +0100 <segfaultfizzbuzz> i saw the spj project
2023-02-19 18:14:52 +0100 <c_wraith> https://groups.csail.mit.edu/cag/crg/papers/sweeney06games.pdf This is what I remember. Funny that it already looks like an SPJ presentation.
2023-02-19 18:15:34 +0100 <segfaultfizzbuzz> oh wow unreal3 is only 250k lines?
2023-02-19 18:16:10 +0100 <segfaultfizzbuzz> i'm surprised i expected 5M+
2023-02-19 18:16:52 +0100machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net)
2023-02-19 18:17:06 +0100 <segfaultfizzbuzz> lol "current GPUs are 16-wide to 48 wide!"
2023-02-19 18:18:39 +0100 <segfaultfizzbuzz> good quote: "There is not a simple set of 'hotspots' to optimize!"
2023-02-19 18:19:40 +0100 <sm> segfaultfizzbuzz: how about the original functional programming paper
2023-02-19 18:21:03 +0100 <segfaultfizzbuzz> another related question is:
2023-02-19 18:21:36 +0100 <segfaultfizzbuzz> if the most "boring" application domain for programming is HFT, where everything is about optimization and systems considerations, what is the opposite of that domain
2023-02-19 18:21:41 +0100hpc(~juzz@ip98-169-35-163.dc.dc.cox.net) (Ping timeout: 255 seconds)
2023-02-19 18:21:50 +0100 <segfaultfizzbuzz> that is to say which domain(s) are the most demanding for the abstraction capabilities of the language
2023-02-19 18:22:03 +0100razetime(~Thunderbi@117.193.3.43) (Remote host closed the connection)
2023-02-19 18:22:20 +0100smmeant https://dl.acm.org/doi/10.1145/359576.359579
2023-02-19 18:23:02 +0100 <segfaultfizzbuzz> sm: i have glanced at this paper but never read it, will try to read it now after i get through sweeney
2023-02-19 18:23:12 +0100 <segfaultfizzbuzz> sweeney hasn't said anything earthshattering aside from the hotspots thing
2023-02-19 18:23:16 +0100hpc(~juzz@ip98-169-35-163.dc.dc.cox.net)
2023-02-19 18:24:10 +0100oxide(~lambda@user/oxide) (Ping timeout: 260 seconds)
2023-02-19 18:26:01 +0100 <segfaultfizzbuzz> sm: what are expressions and what are statements?
2023-02-19 18:27:17 +0100 <sm> also: some stuff at https://squeak.org/documentation > History maybe
2023-02-19 18:27:33 +0100abhixec_(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
2023-02-19 18:27:47 +0100 <segfaultfizzbuzz> sm: bits of history...?
2023-02-19 18:27:59 +0100 <segfaultfizzbuzz> oh the historical papers ok
2023-02-19 18:28:17 +0100 <sm> yup, for programming. language sci-fi
2023-02-19 18:29:01 +0100 <segfaultfizzbuzz> "90% of integer variables in unreal exist to index into arrays"
2023-02-19 18:29:50 +0100 <segfaultfizzbuzz> 50% of loops in unreal engine are functional folds, but then he says 50% are functional comprehensions--what is a functional comprehension?
2023-02-19 18:30:04 +0100 <segfaultfizzbuzz> is that a map?
2023-02-19 18:30:08 +0100Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 248 seconds)
2023-02-19 18:30:12 +0100jarkad(~u@188.163.45.157)
2023-02-19 18:30:13 +0100Lord_of_Life_(~Lord@user/lord-of-life/x-2819915)
2023-02-19 18:30:40 +0100 <geekosaur> it generates values from a template
2023-02-19 18:30:42 +0100 <sm> (also something for lisp, something for apl/k..)
2023-02-19 18:30:59 +0100 <segfaultfizzbuzz> geekosaur: a little more detail please?
2023-02-19 18:31:28 +0100 <geekosaur> look at list comprehensions in haskell or python
2023-02-19 18:31:32 +0100Lord_of_Life_Lord_of_Life
2023-02-19 18:32:00 +0100harveypwca(~harveypwc@2601:246:c180:a570:3828:d8:e523:3f67)
2023-02-19 18:32:27 +0100gurkenglas(~gurkengla@dynamic-046-114-183-040.46.114.pool.telefonica.de) (Ping timeout: 248 seconds)
2023-02-19 18:32:50 +0100 <segfaultfizzbuzz> is a functional container the transformation of a value with a container type into another value with the same container type but a potentially distinct distinct inner types?
2023-02-19 18:32:58 +0100 <segfaultfizzbuzz> *functional comprehension i mean
2023-02-19 18:33:16 +0100jarkadjarkad__
2023-02-19 18:33:31 +0100 <geekosaur> given an input generator of some kind (typically a list of simple values like [0..], it generates more complex values. so in Haskell [ f x + x | x <- [0..] ], `f x + x` is the template and `x` the original list. but there might be multiple lists involved, etc.
2023-02-19 18:33:35 +0100jarkad__jarkad
2023-02-19 18:34:39 +0100 <geekosaur> https://paste.tomsmeding.com/Sd3Wq4Qy
2023-02-19 18:34:45 +0100 <segfaultfizzbuzz> sweeny says: "accessing circularly entailed values causes thunk reentry (divergence) rather than just returning the wrong value" -- what is this?
2023-02-19 18:37:20 +0100 <geekosaur> sounds like a circular list (the last element links back to the start of the list) causes an infinite loop?
2023-02-19 18:37:31 +0100 <hellwolf[m]> my secret dream would be that one programming language, one intermediate representation, and many machines that interpret it in different ways.
2023-02-19 18:37:31 +0100 <hellwolf[m]> One of them can do elastic scaling such that it can detect "hot path" and putting more computing resources during its production cycle.
2023-02-19 18:37:54 +0100 <geekosaur> > repeat [1,2,3] -- this kind of list, but in a lazy language it doesn't necessarily diverge
2023-02-19 18:37:55 +0100 <lambdabot> [[1,2,3],[1,2,3],[1,2,3],[1,2,3],[1,2,3],[1,2,3],[1,2,3],[1,2,3],[1,2,3],[1,...
2023-02-19 18:38:07 +0100 <geekosaur> hm, not quite
2023-02-19 18:38:07 +0100 <segfaultfizzbuzz> hellwolf[m]: agreed, plus you could reveal to the compiler which resources were available at some time and it would shape the program to fit available resources,...
2023-02-19 18:38:27 +0100 <segfaultfizzbuzz> what is diverge?
2023-02-19 18:38:51 +0100 <geekosaur> fail to produce a result (infinite loop, exception, whatever)
2023-02-19 18:39:31 +0100notzmv(~zmv@user/notzmv)
2023-02-19 18:39:35 +0100gurkenglas(~gurkengla@dynamic-046-114-178-211.46.114.pool.telefonica.de)
2023-02-19 18:40:31 +0100 <segfaultfizzbuzz> but he says specifically "re-entry"...?
2023-02-19 18:41:01 +0100 <geekosaur> that's where it loops
2023-02-19 18:41:43 +0100 <geekosaur> > let l = [1,2,3] ++ l in l
2023-02-19 18:41:44 +0100 <lambdabot> [1,2,3,1,2,3,1,2,3,1,2,3,1,2,3,1,2,3,1,2,3,1,2,3,1,2,3,1,2,3,1,2,3,1,2,3,1,2...
2023-02-19 18:41:54 +0100 <segfaultfizzbuzz> i mean, this sentence to me reads as "produces an infinite loop rather than an infinite loop"
2023-02-19 18:42:13 +0100 <geekosaur> in a lazy language it doesn't necessarily diverge, in a strict language it will always diverge
2023-02-19 18:42:38 +0100 <segfaultfizzbuzz> because the lazy language doesn't starve other threads?
2023-02-19 18:42:45 +0100 <segfaultfizzbuzz> and the other thread could generate a termination condition?
2023-02-19 18:42:57 +0100 <geekosaur> because the lazy language cna proceed if it produces any values before looping
2023-02-19 18:43:37 +0100 <geekosaur> and an outer computation can therefore "choose" to stop using values based on some outer condition, as lambdabot does whe n it has a sufficient line length for output
2023-02-19 18:43:48 +0100 <hellwolf[m]> hmm, would any program ever satisfy the property ofsum [1..] == -1/12 per https://en.wikipedia.org/wiki/1_%2B_2_%2B_3_%2B_4_%2B_%E2%8B%AF?
2023-02-19 18:44:02 +0100 <geekosaur> but with strict evaluation it will try to produce the whole list immediately, and fail because it's infinite
2023-02-19 18:44:03 +0100 <segfaultfizzbuzz> hellwolf[m]: lol
2023-02-19 18:44:40 +0100hellwolf[m]wonder why, in haskell it seems hanging :?
2023-02-19 18:44:56 +0100hellwolf[m] * wonder why, in haskell it seems hanging sum [1..] :?
2023-02-19 18:45:04 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 18:45:55 +0100 <monochrom> Because Haskell is not Wolfram Alpha.
2023-02-19 18:46:01 +0100 <segfaultfizzbuzz> hellwolf[m]: i think if you can elaborate on what would be desirable behavior here more generally, this would be a great entry in the programming language scifi section of my library :-)
2023-02-19 18:46:13 +0100 <APic> Sadly
2023-02-19 18:46:52 +0100 <monochrom> So even [x | x <- [1..], x < 0] is divergence rather than the "intuitive" empty list.
2023-02-19 18:46:57 +0100 <segfaultfizzbuzz> btw the "cutoff regularization" of the wikipedia entry he linked to is fascinating (and may actually be a step towards a language scifi feature)
2023-02-19 18:47:00 +0100Inst(~Inst@2601:6c4:4081:54f0:d621:5cdd:9051:c240) (Read error: Connection reset by peer)
2023-02-19 18:47:40 +0100 <hellwolf[m]> we should totally implement a CutOffRegulatableList
2023-02-19 18:47:41 +0100 <hellwolf[m]> * we should totally implement a CutOffRegulatableList
2023-02-19 18:52:22 +0100 <geekosaur> gotta wonder just how far one could push a fancier simple-reflect
2023-02-19 18:52:39 +0100oxide(~lambda@user/oxide)
2023-02-19 18:55:06 +0100segfaultfizzbuzz(~segfaultf@108.211.201.53) (Ping timeout: 255 seconds)
2023-02-19 18:59:31 +0100azimut(~azimut@gateway/tor-sasl/azimut) (Remote host closed the connection)
2023-02-19 18:59:32 +0100FinnElija(~finn_elij@user/finn-elija/x-0085643) (Remote host closed the connection)
2023-02-19 18:59:43 +0100emmanuelux_(~emmanuelu@user/emmanuelux) (Read error: Connection reset by peer)
2023-02-19 18:59:45 +0100wroathe(~wroathe@user/wroathe) (Ping timeout: 260 seconds)
2023-02-19 19:00:32 +0100FinnElija(~finn_elij@user/finn-elija/x-0085643)
2023-02-19 19:00:41 +0100azimut(~azimut@gateway/tor-sasl/azimut)
2023-02-19 19:00:52 +0100emmanuelux_(~emmanuelu@user/emmanuelux)
2023-02-19 19:02:15 +0100shriekingnoise(~shrieking@186.137.175.87) (Ping timeout: 252 seconds)
2023-02-19 19:03:16 +0100 <monochrom> There is probably something about the combination of parametricity, sum being parametrically polymorphic, and the halting problem that requires sum [1..] to diverge. Note that Wolfram Alpha (and Mathematica) is free from parametricity, hell it's probably free from static typing altogether.
2023-02-19 19:04:20 +0100 <monochrom> This also implies that humanity will not settle for one single language that owns them all.
2023-02-19 19:05:03 +0100 <darkling> IIRC, the last time someone tried that, the tower fell down. :)
2023-02-19 19:05:14 +0100 <monochrom> hee hee
2023-02-19 19:05:39 +0100slack1256(~slack1256@186.11.53.84)
2023-02-19 19:05:44 +0100 <darkling> Well, either that, or we ended up with Volapük.
2023-02-19 19:07:15 +0100ddellacosta(~ddellacos@146.70.166.10) (Ping timeout: 255 seconds)
2023-02-19 19:07:27 +0100sagax(~sagax_nb@user/sagax)
2023-02-19 19:07:57 +0100segfaultfizzbuzz(~segfaultf@108.211.201.53)
2023-02-19 19:08:01 +0100 <segfaultfizzbuzz> tomsmeding: so i would say that assembly doesn't meet the "minimal programming language" criterion because the whole register thing is needlessly complex
2023-02-19 19:09:20 +0100ddellacosta(~ddellacos@146.70.166.221)
2023-02-19 19:10:57 +0100 <slack1256> What is the option to print arrow multiplicities on ghci?
2023-02-19 19:14:57 +0100_leo___(~emmanuelu@user/emmanuelux)
2023-02-19 19:17:04 +0100 <geekosaur> I don't see a specific option, beyond LinearTypes. I think we did determine the other day that :t doesn't show multiplicity in at least some cases
2023-02-19 19:17:37 +0100 <geekosaur> if you find a case where it should show multiplicity with LinearTypes enabled but it doesn't, consider filing a bug
2023-02-19 19:17:59 +0100xacktm(~xacktm@user/xacktm) (Ping timeout: 246 seconds)
2023-02-19 19:18:01 +0100emmanuelux_(~emmanuelu@user/emmanuelux) (Ping timeout: 252 seconds)
2023-02-19 19:19:06 +0100 <slack1256> Gotcha!
2023-02-19 19:20:01 +0100andreas303(andreas303@ip227.orange.bnc4free.com) (Ping timeout: 268 seconds)
2023-02-19 19:20:19 +0100raehik(~raehik@cpc95906-rdng25-2-0-cust156.15-3.cable.virginm.net) (Remote host closed the connection)
2023-02-19 19:20:38 +0100econo(uid147250@user/econo)
2023-02-19 19:20:43 +0100raehik(~raehik@cpc95906-rdng25-2-0-cust156.15-3.cable.virginm.net)
2023-02-19 19:21:18 +0100wroathe(~wroathe@207-153-38-140.fttp.usinternet.com)
2023-02-19 19:21:18 +0100wroathe(~wroathe@207-153-38-140.fttp.usinternet.com) (Changing host)
2023-02-19 19:21:18 +0100wroathe(~wroathe@user/wroathe)
2023-02-19 19:21:48 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Remote host closed the connection)
2023-02-19 19:22:20 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 19:24:31 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Read error: Connection reset by peer)
2023-02-19 19:24:36 +0100myyo_(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 19:28:47 +0100myyo_(~myyo@71-211-142-215.hlrn.qwest.net) (Ping timeout: 248 seconds)
2023-02-19 19:29:08 +0100czy(~user@host-140-26.ilcub310.champaign.il.us.clients.pavlovmedia.net)
2023-02-19 19:30:58 +0100merijn(~merijn@86-86-29-250.fixed.kpn.net)
2023-02-19 19:31:26 +0100mechap(~mechap@user/mechap)
2023-02-19 19:32:47 +0100oxide(~lambda@user/oxide) (Quit: oxide)
2023-02-19 19:33:41 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 19:33:50 +0100abhixec_(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Quit: leaving)
2023-02-19 19:34:23 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
2023-02-19 19:34:42 +0100raehik(~raehik@cpc95906-rdng25-2-0-cust156.15-3.cable.virginm.net) (Ping timeout: 255 seconds)
2023-02-19 19:34:42 +0100segfaultfizzbuzz(~segfaultf@108.211.201.53) (Ping timeout: 255 seconds)
2023-02-19 19:35:31 +0100justsomeguy(~justsomeg@user/justsomeguy)
2023-02-19 19:36:31 +0100segfaultfizzbuzz(~segfaultf@108.211.201.53)
2023-02-19 19:36:57 +0100merijn(~merijn@86-86-29-250.fixed.kpn.net) (Ping timeout: 255 seconds)
2023-02-19 19:39:50 +0100 <eldritchcookie[m> how hard is it to make a graphical program in haskell?
2023-02-19 19:41:04 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2023-02-19 19:41:31 +0100czy(~user@host-140-26.ilcub310.champaign.il.us.clients.pavlovmedia.net) (Remote host closed the connection)
2023-02-19 19:42:57 +0100raehik(~raehik@cpc95906-rdng25-2-0-cust156.15-3.cable.virginm.net)
2023-02-19 19:43:30 +0100dolio(~dolio@130.44.134.54) (Quit: ZNC 1.8.2 - https://znc.in)
2023-02-19 19:44:29 +0100 <segfaultfizzbuzz> eldritchcookie[m: https://hub.darcs.net/linearity/pplmonad
2023-02-19 19:45:11 +0100dolio(~dolio@130.44.134.54)
2023-02-19 19:46:26 +0100p0lyph3m(~polyphem@2a02:810d:840:8754:4d31:9178:35f:6608)
2023-02-19 19:47:30 +0100 <hellwolf[m]> <eldritchcookie[m> "how hard is it to make a..." <- not at all, need only 10 lines, check out
2023-02-19 19:47:30 +0100 <hellwolf[m]> https://github.com/haskell-game/tiny-games-hs/tree/main/hackage/brickbreaker
2023-02-19 19:47:55 +0100anpad(~pandeyan@user/anpad) (Ping timeout: 260 seconds)
2023-02-19 19:48:31 +0100 <hellwolf[m]> If you mean GUI app, I guess other people can answer for you. I doubt it'd be difficult.
2023-02-19 19:54:35 +0100raehik(~raehik@cpc95906-rdng25-2-0-cust156.15-3.cable.virginm.net) (Ping timeout: 260 seconds)
2023-02-19 19:57:26 +0100kenran(~user@user/kenran)
2023-02-19 19:58:18 +0100 <eldritchcookie[m> cool i want to make a program similar to maptool, but i like the terminal so i would want to have my server controllable by commands
2023-02-19 19:58:33 +0100kenran(~user@user/kenran) (Remote host closed the connection)
2023-02-19 19:59:01 +0100 <eldritchcookie[m> how can i check to see if a server is up?
2023-02-19 19:59:46 +0100 <c_wraith> typically you just see if you can open the TCP connection. (unless you're not using a TCP-based protocol)
2023-02-19 20:02:24 +0100 <segfaultfizzbuzz> this is potentially a silly question: some people have writtten uh, quantum programming languages,... please don't throw tomatoes here but was anything learned from that enterprise which can actually be used with normal programming languages...?
2023-02-19 20:02:36 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-02-19 20:03:31 +0100mechap(~mechap@user/mechap) (Ping timeout: 246 seconds)
2023-02-19 20:03:33 +0100 <geekosaur> they've discovered some new techniques for simulation of quantum computing. nothing much in the sense of languages, though:P as digital computing is significantly different from analog computing, so also quantum computing
2023-02-19 20:05:46 +0100mechap(~mechap@user/mechap)
2023-02-19 20:06:01 +0100 <segfaultfizzbuzz> i was thinking that the pure functional paradigm is best for reversible computations and imperative is best for non-reversible...?
2023-02-19 20:06:16 +0100mechap(~mechap@user/mechap) (Max SendQ exceeded)
2023-02-19 20:06:44 +0100mechap(~mechap@user/mechap)
2023-02-19 20:06:54 +0100 <geekosaur> someone else would probably have to answer that in detail, but I'd expect them to handle different kinds of "reversible"
2023-02-19 20:07:18 +0100mechap(~mechap@user/mechap) (Max SendQ exceeded)
2023-02-19 20:07:46 +0100mechap(~mechap@user/mechap)
2023-02-19 20:08:04 +0100 <geekosaur> consider that `const` isn't reversible unless you keep the original value around
2023-02-19 20:08:23 +0100mikoto-chan(~mikoto-ch@85-76-71-143-nat.elisa-mobile.fi)
2023-02-19 20:08:24 +0100mechap(~mechap@user/mechap) (Max SendQ exceeded)
2023-02-19 20:08:53 +0100mechap(~mechap@user/mechap)
2023-02-19 20:09:32 +0100mechap(~mechap@user/mechap) (Max SendQ exceeded)
2023-02-19 20:10:00 +0100mechap(~mechap@user/mechap)
2023-02-19 20:10:23 +0100 <segfaultfizzbuzz> that is to say, imperative programs look more like random noise if you could watch RAM
2023-02-19 20:10:30 +0100 <segfaultfizzbuzz> whereas functional programs, you would notice patterns
2023-02-19 20:10:39 +0100mechap(~mechap@user/mechap) (Max SendQ exceeded)
2023-02-19 20:13:05 +0100mechap(~mechap@user/mechap)
2023-02-19 20:14:14 +0100mechap(~mechap@user/mechap) (Max SendQ exceeded)
2023-02-19 20:14:43 +0100mechap(~mechap@user/mechap)
2023-02-19 20:16:05 +0100mechap(~mechap@user/mechap) (Max SendQ exceeded)
2023-02-19 20:16:35 +0100mechap(~mechap@user/mechap)
2023-02-19 20:17:17 +0100mechap(~mechap@user/mechap) (Max SendQ exceeded)
2023-02-19 20:19:10 +0100Sgeo(~Sgeo@user/sgeo)
2023-02-19 20:24:45 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2023-02-19 20:25:16 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Remote host closed the connection)
2023-02-19 20:25:50 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 20:25:51 +0100segfaultfizzbuzz(~segfaultf@108.211.201.53) (Ping timeout: 252 seconds)
2023-02-19 20:25:51 +0100alphabeta(~kilolympu@61-194-35-233.ip.hotelswifi.jp)
2023-02-19 20:26:00 +0100kilolympus(~kilolympu@213.144.144.24) (Ping timeout: 268 seconds)
2023-02-19 20:26:15 +0100SenFache(~sauvin@user/Sauvin) (Read error: Connection reset by peer)
2023-02-19 20:27:20 +0100Sauvin(~sauvin@user/Sauvin)
2023-02-19 20:27:40 +0100justsomeguy(~justsomeg@user/justsomeguy) (Ping timeout: 246 seconds)
2023-02-19 20:28:26 +0100justsomeguy(~justsomeg@user/justsomeguy)
2023-02-19 20:30:04 +0100mechap(~mechap@user/mechap)
2023-02-19 20:30:15 +0100wootehfoot(~wootehfoo@user/wootehfoot) (Ping timeout: 252 seconds)
2023-02-19 20:30:30 +0100wroathe(~wroathe@user/wroathe) (Ping timeout: 255 seconds)
2023-02-19 20:30:34 +0100mechap(~mechap@user/mechap) (Max SendQ exceeded)
2023-02-19 20:30:45 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Ping timeout: 260 seconds)
2023-02-19 20:40:51 +0100justsomeguy(~justsomeg@user/justsomeguy) (Quit: WeeChat 3.6)
2023-02-19 20:43:20 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 20:44:47 +0100mikoto-chan(~mikoto-ch@85-76-71-143-nat.elisa-mobile.fi) (Ping timeout: 255 seconds)
2023-02-19 20:45:22 +0100dcoutts_(~duncan@86.167.90.212)
2023-02-19 20:45:34 +0100mikoto-chan(~mikoto-ch@85-76-71-143-nat.elisa-mobile.fi)
2023-02-19 20:45:55 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Read error: Connection reset by peer)
2023-02-19 20:46:03 +0100acidjnk(~acidjnk@2003:d6:e715:c436:2c63:9e78:5d9e:e9c9)
2023-02-19 20:46:06 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 20:46:35 +0100falafel(~falafel@2607:fb91:143f:e47f:7fc6:7d11:1de3:df27)
2023-02-19 20:48:12 +0100harveypwca(~harveypwc@2601:246:c180:a570:3828:d8:e523:3f67) (Quit: Leaving)
2023-02-19 20:52:51 +0100wroathe(~wroathe@50.205.197.50)
2023-02-19 20:52:51 +0100wroathe(~wroathe@50.205.197.50) (Changing host)
2023-02-19 20:52:51 +0100wroathe(~wroathe@user/wroathe)
2023-02-19 20:53:35 +0100sudden(~cat@user/sudden) (Ping timeout: 264 seconds)
2023-02-19 20:53:55 +0100dcoutts_(~duncan@86.167.90.212) (Remote host closed the connection)
2023-02-19 20:54:02 +0100sudden(~cat@user/sudden)
2023-02-19 20:54:17 +0100dcoutts_(~duncan@host86-167-90-212.range86-167.btcentralplus.com)
2023-02-19 21:02:23 +0100mikoto-chan(~mikoto-ch@85-76-71-143-nat.elisa-mobile.fi) (Ping timeout: 268 seconds)
2023-02-19 21:04:32 +0100raehik(~raehik@cpc95906-rdng25-2-0-cust156.15-3.cable.virginm.net)
2023-02-19 21:09:21 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2023-02-19 21:14:36 +0100slack1256(~slack1256@186.11.53.84) (Ping timeout: 255 seconds)
2023-02-19 21:19:27 +0100falafel(~falafel@2607:fb91:143f:e47f:7fc6:7d11:1de3:df27) (Remote host closed the connection)
2023-02-19 21:19:47 +0100falafel(~falafel@2607:fb91:143f:e47f:f620:28ba:bca9:7a58)
2023-02-19 21:24:23 +0100falafel(~falafel@2607:fb91:143f:e47f:f620:28ba:bca9:7a58) (Ping timeout: 255 seconds)
2023-02-19 21:25:04 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Remote host closed the connection)
2023-02-19 21:25:21 +0100oxide(~lambda@user/oxide)
2023-02-19 21:25:36 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 21:27:32 +0100alphabeta(~kilolympu@61-194-35-233.ip.hotelswifi.jp) (Ping timeout: 255 seconds)
2023-02-19 21:27:40 +0100jjhoo_jjhoo
2023-02-19 21:29:52 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Ping timeout: 252 seconds)
2023-02-19 21:32:11 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex)
2023-02-19 21:33:48 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl)
2023-02-19 21:37:01 +0100segfaultfizzbuzz(~segfaultf@108.211.201.53)
2023-02-19 21:40:00 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Quit: leaving)
2023-02-19 21:40:00 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl) (Ping timeout: 268 seconds)
2023-02-19 21:41:52 +0100waleee(~waleee@h-176-10-137-138.NA.cust.bahnhof.se)
2023-02-19 21:42:55 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 21:47:28 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Ping timeout: 252 seconds)
2023-02-19 21:55:33 +0100dcoutts_(~duncan@host86-167-90-212.range86-167.btcentralplus.com) (Ping timeout: 255 seconds)
2023-02-19 21:57:49 +0100npmania(~Thunderbi@138.199.21.232) (Remote host closed the connection)
2023-02-19 21:58:58 +0100eggplantade(~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net) (Remote host closed the connection)
2023-02-19 22:00:09 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 22:00:16 +0100dcoutts_(~duncan@host86-167-90-212.range86-167.btcentralplus.com)
2023-02-19 22:02:24 +0100raehik(~raehik@cpc95906-rdng25-2-0-cust156.15-3.cable.virginm.net) (Ping timeout: 248 seconds)
2023-02-19 22:04:40 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Ping timeout: 260 seconds)
2023-02-19 22:05:43 +0100raehik(~raehik@cpc95906-rdng25-2-0-cust156.15-3.cable.virginm.net)
2023-02-19 22:18:52 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 22:22:06 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection)
2023-02-19 22:22:07 +0100segfaultfizzbuzz(~segfaultf@108.211.201.53) (Ping timeout: 246 seconds)
2023-02-19 22:23:11 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex)
2023-02-19 22:23:12 +0100waleee(~waleee@h-176-10-137-138.NA.cust.bahnhof.se) (Ping timeout: 248 seconds)
2023-02-19 22:23:13 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Ping timeout: 252 seconds)
2023-02-19 22:27:35 +0100andrewboltachev(~andrey@178.141.125.176) (Quit: Leaving.)
2023-02-19 22:30:06 +0100jmdaemon(~jmdaemon@user/jmdaemon)
2023-02-19 22:30:32 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7)
2023-02-19 22:35:22 +0100mauke(~mauke@user/mauke) (Read error: Connection reset by peer)
2023-02-19 22:35:28 +0100mauke_(~mauke@user/mauke)
2023-02-19 22:36:20 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 22:36:20 +0100mauke_mauke
2023-02-19 22:36:45 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Ping timeout: 252 seconds)
2023-02-19 22:39:37 +0100oxide(~lambda@user/oxide) (Ping timeout: 246 seconds)
2023-02-19 22:39:57 +0100trev(~trev@user/trev) (Remote host closed the connection)
2023-02-19 22:40:50 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Ping timeout: 260 seconds)
2023-02-19 22:43:35 +0100anpad(~pandeyan@user/anpad)
2023-02-19 22:48:43 +0100ubert(~Thunderbi@p200300ecdf1301b3ab5830a245f8dddb.dip0.t-ipconnect.de) (Ping timeout: 246 seconds)
2023-02-19 22:48:55 +0100ubert(~Thunderbi@p200300ecdf1301aeed9235aafc85dd9a.dip0.t-ipconnect.de)
2023-02-19 22:49:19 +0100waleee(~waleee@176.10.137.138)
2023-02-19 22:49:22 +0100oxide(~lambda@user/oxide)
2023-02-19 22:51:47 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2023-02-19 22:54:08 +0100gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c) (Quit: WeeChat 3.8)
2023-02-19 22:54:28 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 22:54:28 +0100opticblast(~Thunderbi@172.58.85.230)
2023-02-19 22:58:53 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Ping timeout: 255 seconds)
2023-02-19 22:59:26 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:bc09:17b4:a9c9:5fe5)
2023-02-19 23:03:13 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.)
2023-02-19 23:03:46 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:bc09:17b4:a9c9:5fe5) (Ping timeout: 246 seconds)
2023-02-19 23:04:20 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10)
2023-02-19 23:06:09 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
2023-02-19 23:07:11 +0100wroathe(~wroathe@user/wroathe) (Quit: leaving)
2023-02-19 23:09:01 +0100waleee(~waleee@176.10.137.138) (Ping timeout: 252 seconds)
2023-02-19 23:10:30 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 23:10:46 +0100xff0x(~xff0x@2405:6580:b080:900:2ba9:89b5:e4d8:5d14)
2023-02-19 23:11:29 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2023-02-19 23:15:05 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Ping timeout: 255 seconds)
2023-02-19 23:27:19 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 23:29:44 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2023-02-19 23:31:45 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Ping timeout: 255 seconds)
2023-02-19 23:31:46 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7)
2023-02-19 23:34:00 +0100eggplantade(~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net)
2023-02-19 23:36:25 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl)
2023-02-19 23:43:37 +0100bgs(~bgs@212-85-160-171.dynamic.telemach.net) (Remote host closed the connection)
2023-02-19 23:44:41 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net)
2023-02-19 23:46:17 +0100eggplantade(~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net) (Remote host closed the connection)
2023-02-19 23:46:52 +0100__monty__(~toonn@user/toonn) (Quit: leaving)
2023-02-19 23:49:03 +0100myyo(~myyo@71-211-142-215.hlrn.qwest.net) (Ping timeout: 248 seconds)
2023-02-19 23:49:24 +0100merijn(~merijn@c-001-001-009.client.esciencecenter.eduvpn.nl) (Ping timeout: 255 seconds)
2023-02-19 23:51:05 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Ping timeout: 255 seconds)
2023-02-19 23:54:16 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2023-02-19 23:56:01 +0100pavonia(~user@user/siracusa)