2025/02/09

2025-02-09 00:07:56 +0100 <peutri> tomsmeding: (followup) currently going with sizeOf (fix id :: a), which is somehow worse-than-partial yet doesn't warn
2025-02-09 00:08:06 +0100sixfourtwelve(~ethanmorg@82.18.82.103) sixfourtwelve
2025-02-09 00:08:38 +0100 <monochrom> Interesting. Did "undefined :: a" cause a warning?
2025-02-09 00:08:44 +0100 <peutri> but is by far the minimal project disruption I found
2025-02-09 00:08:57 +0100 <peutri> yes (because Relude)
2025-02-09 00:09:15 +0100 <monochrom> God, totality police.
2025-02-09 00:09:23 +0100 <peutri> ikr
2025-02-09 00:09:35 +0100 <monochrom> May I be facetious and say "totalitarian" >:)
2025-02-09 00:09:37 +0100 <peutri> and I'm voluntarily signing up for it
2025-02-09 00:11:08 +0100 <peutri> I'm also noticing now `fix id` is shorter than `undefined`, and considering… mmmm… no, better forget that
2025-02-09 00:11:26 +0100 <monochrom> @type fix fix
2025-02-09 00:11:27 +0100 <lambdabot> error:
2025-02-09 00:11:27 +0100 <lambdabot> • Occurs check: cannot construct the infinite type: a ~ a -> a
2025-02-09 00:11:27 +0100 <lambdabot> Expected type: a -> a
2025-02-09 00:12:17 +0100sixfourtwelve(~ethanmorg@82.18.82.103) (Ping timeout: 248 seconds)
2025-02-09 00:12:38 +0100target_i(~target_i@user/target-i/x-6023099) (Quit: leaving)
2025-02-09 00:13:28 +0100 <monochrom> More fairly, on the scale of safety, static error message > runtime error message > no error message
2025-02-09 00:14:14 +0100 <monochrom> So a warning system that simply pushes users away from runtime error (undefined) to no error (fix id) is... You know, the road to hell is paved with well intentions.
2025-02-09 00:17:44 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-09 00:22:35 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 268 seconds)
2025-02-09 00:28:24 +0100benjamin(~benjamin@2a03:4b80:a720:6e10:2961:287b:51c1:b384)
2025-02-09 00:29:12 +0100Cattykitties
2025-02-09 00:29:40 +0100sixfourtwelve(~ethanmorg@82.18.82.103) sixfourtwelve
2025-02-09 00:30:58 +0100hiredman(~hiredman@frontier1.downey.family) (Quit: Lost terminal)
2025-02-09 00:31:34 +0100benjamin(~benjamin@2a03:4b80:a720:6e10:2961:287b:51c1:b384) (Client Quit)
2025-02-09 00:31:53 +0100benjamin(~benjamin@2a03:4b80:a720:6e10:2961:287b:51c1:b384)
2025-02-09 00:31:58 +0100benjamin(~benjamin@2a03:4b80:a720:6e10:2961:287b:51c1:b384) (Remote host closed the connection)
2025-02-09 00:33:58 +0100sixfourtwelve(~ethanmorg@82.18.82.103) (Ping timeout: 252 seconds)
2025-02-09 00:38:33 +0100takuan(~takuan@d8D86B601.access.telenet.be) (Remote host closed the connection)
2025-02-09 00:39:22 +0100 <Leary> If you don't care to heed a warning, you're supposed to ignore or disable it---it is just a /warning/, after all, not an error. Let's not blame x-partial for /wacky dodging/.
2025-02-09 00:42:20 +0100hiredman(~hiredman@frontier1.downey.family) hiredman
2025-02-09 00:43:19 +0100 <monochrom> That would be a much better stance than mine, if not for the same totalitarian police also instituting "no warning by the time you commit" or even -Wall -Werror.
2025-02-09 00:44:08 +0100 <monochrom> So it just means I should be complaining about the policing system rather than the warning system.
2025-02-09 00:50:05 +0100philopsos(~caecilius@user/philopsos) (Ping timeout: 265 seconds)
2025-02-09 00:51:34 +0100sixfourtwelve(~ethanmorg@82.18.82.103) sixfourtwelve
2025-02-09 00:51:55 +0100philopsos(~caecilius@user/philopsos) philopsos
2025-02-09 00:56:45 +0100sixfourtwelve(~ethanmorg@82.18.82.103) (Ping timeout: 276 seconds)
2025-02-09 00:57:15 +0100m1dnight(~m1dnight@d8D861908.access.telenet.be) m1dnight
2025-02-09 00:59:58 +0100 <Leary> Right. I actually understand if people with too much code to review want strict CI to make their life easier, but it should diff with a checked-in record of known/accepted warnings for flexibility.
2025-02-09 01:06:02 +0100mesaoptimizer0(~mesaoptim@user/PapuaHardyNet) (Ping timeout: 265 seconds)
2025-02-09 01:06:02 +0100jathan(~jathan@69.61.93.38) (Ping timeout: 265 seconds)
2025-02-09 01:06:09 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-09 01:10:28 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 244 seconds)
2025-02-09 01:13:34 +0100Maxdamantus(~Maxdamant@user/maxdamantus) (Ping timeout: 244 seconds)
2025-02-09 01:16:53 +0100TMA(tma@twin.jikos.cz) (Ping timeout: 248 seconds)
2025-02-09 01:17:38 +0100mulk(~mulk@pd95141d7.dip0.t-ipconnect.de) (Ping timeout: 265 seconds)
2025-02-09 01:18:05 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 268 seconds)
2025-02-09 01:18:07 +0100m1dnight(~m1dnight@d8D861908.access.telenet.be) (Ping timeout: 265 seconds)
2025-02-09 01:19:49 +0100m1dnight(~m1dnight@d8D861908.access.telenet.be) m1dnight
2025-02-09 01:20:09 +0100mulk(~mulk@pd95141d7.dip0.t-ipconnect.de) mulk
2025-02-09 01:20:15 +0100otbergsten(~otbergste@user/otbergsten) ()
2025-02-09 01:20:20 +0100Maxdamantus(~Maxdamant@user/maxdamantus) Maxdamantus
2025-02-09 01:20:33 +0100L29Ah(~L29Ah@wikipedia/L29Ah) (Ping timeout: 268 seconds)
2025-02-09 01:21:15 +0100jathan(~jathan@2607:1a00:0:19::2:1dc) jathan
2025-02-09 01:25:14 +0100TMA(tma@twin.jikos.cz) TMA
2025-02-09 01:36:05 +0100zerozwro
2025-02-09 01:37:29 +0100L29Ah(~L29Ah@wikipedia/L29Ah) L29Ah
2025-02-09 01:40:00 +0100alx741(~alx741@186.33.188.229)
2025-02-09 01:43:56 +0100yegorc(~yegorc@user/yegorc) yegorc
2025-02-09 01:44:24 +0100aaronv(~aaronv@user/aaronv) aaronv
2025-02-09 01:44:32 +0100Square2(~Square@user/square) Square
2025-02-09 01:44:34 +0100Square3(~Square@user/square) Square
2025-02-09 01:47:00 +0100stiell(~stiell@gateway/tor-sasl/stiell) (Ping timeout: 264 seconds)
2025-02-09 01:47:24 +0100ljdarj1(~Thunderbi@user/ljdarj) ljdarj
2025-02-09 01:47:53 +0100sprotte24(~sprotte24@p200300d16f1e3a00501959556750eb7a.dip0.t-ipconnect.de) (Quit: Leaving)
2025-02-09 01:49:58 +0100stiell(~stiell@gateway/tor-sasl/stiell) stiell
2025-02-09 01:50:19 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 260 seconds)
2025-02-09 01:50:19 +0100ljdarj1ljdarj
2025-02-09 01:54:53 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-09 01:57:47 +0100migas97787(~migas@static.140.65.63.178.clients.your-server.de) migas
2025-02-09 01:59:15 +0100sixfourtwelve(~ethanmorg@82.18.82.103)
2025-02-09 01:59:16 +0100sixfourtwelve(~ethanmorg@82.18.82.103) (Client Quit)
2025-02-09 01:59:24 +0100migas9778(~migas@static.140.65.63.178.clients.your-server.de) (Read error: Connection reset by peer)
2025-02-09 01:59:24 +0100migas97787migas9778
2025-02-09 01:59:33 +0100sixfourtwelve(~ethanmorg@82.18.82.103)
2025-02-09 01:59:41 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 265 seconds)
2025-02-09 02:05:05 +0100alx741(~alx741@186.33.188.229) (Quit: alx741)
2025-02-09 02:21:31 +0100sixfourtwelve(~ethanmorg@82.18.82.103) (Quit: leaving)
2025-02-09 02:21:40 +0100Guest46(~Guest46@149.40.58.147)
2025-02-09 02:25:03 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2025-02-09 02:25:18 +0100acidjnk_new3(~acidjnk@p200300d6e7283f0584678bbe6a824f58.dip0.t-ipconnect.de) (Ping timeout: 268 seconds)
2025-02-09 02:31:17 +0100Guest46(~Guest46@149.40.58.147) (Quit: Client closed)
2025-02-09 02:35:28 +0100califax(~califax@user/califx) (Remote host closed the connection)
2025-02-09 02:36:15 +0100califax(~califax@user/califx) califx
2025-02-09 02:43:37 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-09 02:43:59 +0100Tuplanolla(~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Quit: Leaving.)
2025-02-09 02:48:07 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 268 seconds)
2025-02-09 03:14:18 +0100aaronv(~aaronv@user/aaronv) (Ping timeout: 252 seconds)
2025-02-09 03:18:59 +0100Jeanne-Kamikaze(~Jeanne-Ka@79.127.217.43) Jeanne-Kamikaze
2025-02-09 03:23:35 +0100aaronv(~aaronv@user/aaronv) aaronv
2025-02-09 03:28:07 +0100vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2025-02-09 03:29:14 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 252 seconds)
2025-02-09 03:32:00 +0100gmg(~user@user/gehmehgeh) (Ping timeout: 264 seconds)
2025-02-09 03:32:02 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-09 03:32:10 +0100gmg(~user@user/gehmehgeh) gehmehgeh
2025-02-09 03:36:50 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 268 seconds)
2025-02-09 03:53:33 +0100tavare(~tavare@150.129.88.189)
2025-02-09 03:53:33 +0100tavare(~tavare@150.129.88.189) (Changing host)
2025-02-09 03:53:33 +0100tavare(~tavare@user/tavare) tavare
2025-02-09 04:05:04 +0100op_4(~tslil@user/op-4/x-9116473) (Remote host closed the connection)
2025-02-09 04:05:35 +0100op_4(~tslil@user/op-4/x-9116473) op_4
2025-02-09 04:20:26 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-09 04:23:03 +0100Jeanne-Kamikaze(~Jeanne-Ka@79.127.217.43) (Quit: Leaving)
2025-02-09 04:24:36 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 252 seconds)
2025-02-09 04:47:14 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2025-02-09 04:59:25 +0100jle`(~jle`@2603:8001:3b02:84d4:6618:6c83:b259:edfc) (Ping timeout: 252 seconds)
2025-02-09 05:02:18 +0100Unicorn_Princess(~Unicorn_P@user/Unicorn-Princess/x-3540542) (Remote host closed the connection)
2025-02-09 05:03:48 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 264 seconds)
2025-02-09 05:04:31 +0100TheCoffeMaker(~TheCoffeM@user/thecoffemaker) (Ping timeout: 244 seconds)
2025-02-09 05:08:19 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) bitdex
2025-02-09 05:08:50 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-09 05:13:54 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 272 seconds)
2025-02-09 05:17:57 +0100aaronv(~aaronv@user/aaronv) (Ping timeout: 248 seconds)
2025-02-09 05:22:21 +0100aaronv(~aaronv@user/aaronv) aaronv
2025-02-09 05:32:59 +0100jle`(~jle`@syn-023-240-067-073.res.spectrum.com) jle`
2025-02-09 05:34:54 +0100tri(~tri@2601:182:780:720::55a0)
2025-02-09 05:35:53 +0100 <tri> hi, why is this not working please?
2025-02-09 05:35:55 +0100 <tri> https://paste.tomsmeding.com/jV6JdsBd
2025-02-09 05:36:48 +0100 <tri> it has something to do with 2 parameters passing into zip, but I can't really explain
2025-02-09 05:39:51 +0100dtman34(~dtman34@c-75-72-179-251.hsd1.mn.comcast.net) dtman34
2025-02-09 05:43:45 +0100 <tri> seems like I can only compose 1 input function...
2025-02-09 05:44:02 +0100 <monochrom> Do you accept: getTotalDistance xs ys = sum (zipWith (\(left, right) -> abs $ left -right) xs ys)
2025-02-09 05:45:48 +0100 <tri> yea that works, I'm just trying to make it work using function composition. I forgot what concept force me to use 1 input function to compose, I have to look it up
2025-02-09 05:47:13 +0100yegorc(~yegorc@user/yegorc) (Quit: Leaving)
2025-02-09 05:47:30 +0100 <tri> btw I've just come back to Haskell after a long break, and still seeing you here helping people out. Thank you
2025-02-09 05:51:33 +0100encyde(~ensyde@2601:5c6:c200:6dc0::16fe)
2025-02-09 05:54:10 +0100aforemny_(~aforemny@2001:9e8:6cdf:f800:9bf4:7ea7:4c6a:c80f) aforemny
2025-02-09 05:55:19 +0100aforemny(~aforemny@2001:9e8:6cc0:9f00:f26a:4821:630d:3b0c) (Ping timeout: 260 seconds)
2025-02-09 05:56:34 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-09 05:57:26 +0100 <tri> oh the (.) is actually a function, which takes two 1-input functions
2025-02-09 05:57:46 +0100 <tri> so that's why zip was failing because it is a 2-input function
2025-02-09 06:01:02 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 252 seconds)
2025-02-09 06:01:09 +0100 <monochrom> Now to probe the boundary of your understanding, "g xs ys = sum (zipWith f xs ys)" can still be simplified with (.), but only as: g xs = sum . zipWith f xs
2025-02-09 06:06:27 +0100 <tri> hmm ok
2025-02-09 06:07:41 +0100jle`(~jle`@syn-023-240-067-073.res.spectrum.com) (Quit: WeeChat 4.5.1)
2025-02-09 06:14:10 +0100jle`(~jle`@2603:8001:3b00:11:8cd8:7ce2:93ee:a30) jle`
2025-02-09 06:18:58 +0100Loshki(~Loshki@c-98-42-126-198.hsd1.ca.comcast.net)
2025-02-09 06:19:02 +0100Loshki(~Loshki@c-98-42-126-198.hsd1.ca.comcast.net) (Leaving)
2025-02-09 06:27:17 +0100lisbeths(uid135845@id-135845.lymington.irccloud.com) lisbeths
2025-02-09 06:28:07 +0100weary-traveler(~user@user/user363627) (Quit: Konversation terminated!)
2025-02-09 06:34:52 +0100weary-traveler(~user@user/user363627) user363627
2025-02-09 06:35:00 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 264 seconds)
2025-02-09 06:41:06 +0100 <tri> https://paste.tomsmeding.com/XPlMpEUw
2025-02-09 06:42:09 +0100 <tri> Cannot apply expression of type ‘m0 a0’
2025-02-09 06:42:09 +0100 <tri> to a visible type argument ‘[Int]
2025-02-09 06:42:20 +0100 <tri> how could I fix this please? I don't understand the error message, especially m0 and a0
2025-02-09 06:42:32 +0100 <c_wraith> Add parens
2025-02-09 06:42:36 +0100 <c_wraith> return (...)
2025-02-09 06:42:47 +0100 <int-e> :t return read
2025-02-09 06:42:48 +0100 <lambdabot> (Monad m, Read a) => m (String -> a)
2025-02-09 06:43:01 +0100 <int-e> that's the m0 a0, more or less
2025-02-09 06:43:18 +0100 <int-e> the "expression of type ‘m0 a0’" I mean
2025-02-09 06:43:44 +0100 <int-e> you can drop the @[Int], but you still need parentheses
2025-02-09 06:44:14 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 244 seconds)
2025-02-09 06:44:21 +0100 <int-e> (the type will then be taken from the type signature or `readList`)
2025-02-09 06:44:29 +0100 <int-e> s/or/of/
2025-02-09 06:44:38 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-09 06:45:36 +0100 <int-e> tri: keep in mind that in Haskell `return` is a function, not syntax.
2025-02-09 06:46:09 +0100 <monochrom> Conversely, I see people writing in C "return(x+y)" all the time. :)
2025-02-09 06:47:55 +0100 <tri> ah! thank you. It's been a long time since I last used Haskell :)
2025-02-09 06:49:14 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 268 seconds)