2025/02/08

Newest at the top

2025-02-09 00:50:05 +0100philopsos(~caecilius@user/philopsos) (Ping timeout: 265 seconds)
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: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:42:20 +0100hiredman(~hiredman@frontier1.downey.family) hiredman
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:38:33 +0100takuan(~takuan@d8D86B601.access.telenet.be) (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:31:58 +0100benjamin(~benjamin@2a03:4b80:a720:6e10:2961:287b:51c1:b384) (Remote host closed the connection)
2025-02-09 00:31:53 +0100benjamin(~benjamin@2a03:4b80:a720:6e10:2961:287b:51c1:b384)
2025-02-09 00:31:34 +0100benjamin(~benjamin@2a03:4b80:a720:6e10:2961:287b:51c1:b384) (Client Quit)
2025-02-09 00:30:58 +0100hiredman(~hiredman@frontier1.downey.family) (Quit: Lost terminal)
2025-02-09 00:29:40 +0100sixfourtwelve(~ethanmorg@82.18.82.103) sixfourtwelve
2025-02-09 00:29:12 +0100Cattykitties
2025-02-09 00:28:24 +0100benjamin(~benjamin@2a03:4b80:a720:6e10:2961:287b:51c1:b384)
2025-02-09 00:22:35 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 268 seconds)
2025-02-09 00:17:44 +0100alfiee(~alfiee@user/alfiee) alfiee
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:13:28 +0100 <monochrom> More fairly, on the scale of safety, static error message > runtime error message > no error message
2025-02-09 00:12:38 +0100target_i(~target_i@user/target-i/x-6023099) (Quit: leaving)
2025-02-09 00:12:17 +0100sixfourtwelve(~ethanmorg@82.18.82.103) (Ping timeout: 248 seconds)
2025-02-09 00:11:27 +0100 <lambdabot> Expected type: a -> a
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> error:
2025-02-09 00:11:26 +0100 <monochrom> @type fix fix
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:09:37 +0100 <peutri> and I'm voluntarily signing up for it
2025-02-09 00:09:35 +0100 <monochrom> May I be facetious and say "totalitarian" >:)
2025-02-09 00:09:23 +0100 <peutri> ikr
2025-02-09 00:09:15 +0100 <monochrom> God, totality police.
2025-02-09 00:08:57 +0100 <peutri> yes (because Relude)
2025-02-09 00:08:44 +0100 <peutri> but is by far the minimal project disruption I found
2025-02-09 00:08:38 +0100 <monochrom> Interesting. Did "undefined :: a" cause a warning?
2025-02-09 00:08:06 +0100sixfourtwelve(~ethanmorg@82.18.82.103) sixfourtwelve
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-08 23:46:54 +0100sixfourtwelve(~ethanmorg@82.18.82.103) (Ping timeout: 246 seconds)
2025-02-08 23:33:43 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 245 seconds)
2025-02-08 23:29:39 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-08 23:25:04 +0100vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 260 seconds)
2025-02-08 23:11:39 +0100m1dnight(~m1dnight@d8D861908.access.telenet.be) (Ping timeout: 260 seconds)
2025-02-08 23:06:29 +0100TheCoffeMaker(~TheCoffeM@user/thecoffemaker) TheCoffeMaker
2025-02-08 23:05:12 +0100Sgeo(~Sgeo@user/sgeo) Sgeo
2025-02-08 23:03:06 +0100TheCoffeMaker(~TheCoffeM@user/thecoffemaker) (Read error: Connection reset by peer)
2025-02-08 23:02:13 +0100TheCoffeMaker(~TheCoffeM@user/thecoffemaker) TheCoffeMaker
2025-02-08 22:48:14 +0100m1dnight(~m1dnight@d8D861908.access.telenet.be) m1dnight
2025-02-08 22:46:34 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 260 seconds)
2025-02-08 22:45:13 +0100Sgeo(~Sgeo@user/sgeo) (Read error: Connection reset by peer)
2025-02-08 22:41:55 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-08 22:40:01 +0100machinedgod(~machinedg@d108-173-18-100.abhsia.telus.net) (Ping timeout: 248 seconds)
2025-02-08 22:25:29 +0100sixfourtwelve(~ethanmorg@82.18.82.103) sixfourtwelve
2025-02-08 22:24:29 +0100sixfourtwelve(~ethanmorg@82.18.82.103) ()