| 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 +0100 | sixfourtwelve | (~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 +0100 | sixfourtwelve | (~ethanmorg@82.18.82.103) (Ping timeout: 248 seconds) |
| 2025-02-09 00:12:38 +0100 | target_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 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-02-09 00:22:35 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 268 seconds) |
| 2025-02-09 00:28:24 +0100 | benjamin | (~benjamin@2a03:4b80:a720:6e10:2961:287b:51c1:b384) |
| 2025-02-09 00:29:12 +0100 | Catty | kitties |
| 2025-02-09 00:29:40 +0100 | sixfourtwelve | (~ethanmorg@82.18.82.103) sixfourtwelve |
| 2025-02-09 00:30:58 +0100 | hiredman | (~hiredman@frontier1.downey.family) (Quit: Lost terminal) |
| 2025-02-09 00:31:34 +0100 | benjamin | (~benjamin@2a03:4b80:a720:6e10:2961:287b:51c1:b384) (Client Quit) |
| 2025-02-09 00:31:53 +0100 | benjamin | (~benjamin@2a03:4b80:a720:6e10:2961:287b:51c1:b384) |
| 2025-02-09 00:31:58 +0100 | benjamin | (~benjamin@2a03:4b80:a720:6e10:2961:287b:51c1:b384) (Remote host closed the connection) |
| 2025-02-09 00:33:58 +0100 | sixfourtwelve | (~ethanmorg@82.18.82.103) (Ping timeout: 252 seconds) |
| 2025-02-09 00:38:33 +0100 | takuan | (~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 +0100 | hiredman | (~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 +0100 | philopsos | (~caecilius@user/philopsos) (Ping timeout: 265 seconds) |
| 2025-02-09 00:51:34 +0100 | sixfourtwelve | (~ethanmorg@82.18.82.103) sixfourtwelve |
| 2025-02-09 00:51:55 +0100 | philopsos | (~caecilius@user/philopsos) philopsos |
| 2025-02-09 00:56:45 +0100 | sixfourtwelve | (~ethanmorg@82.18.82.103) (Ping timeout: 276 seconds) |
| 2025-02-09 00:57:15 +0100 | m1dnight | (~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 +0100 | mesaoptimizer0 | (~mesaoptim@user/PapuaHardyNet) (Ping timeout: 265 seconds) |
| 2025-02-09 01:06:02 +0100 | jathan | (~jathan@69.61.93.38) (Ping timeout: 265 seconds) |
| 2025-02-09 01:06:09 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-02-09 01:10:28 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 244 seconds) |
| 2025-02-09 01:13:34 +0100 | Maxdamantus | (~Maxdamant@user/maxdamantus) (Ping timeout: 244 seconds) |
| 2025-02-09 01:16:53 +0100 | TMA | (tma@twin.jikos.cz) (Ping timeout: 248 seconds) |
| 2025-02-09 01:17:38 +0100 | mulk | (~mulk@pd95141d7.dip0.t-ipconnect.de) (Ping timeout: 265 seconds) |
| 2025-02-09 01:18:05 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 268 seconds) |
| 2025-02-09 01:18:07 +0100 | m1dnight | (~m1dnight@d8D861908.access.telenet.be) (Ping timeout: 265 seconds) |
| 2025-02-09 01:19:49 +0100 | m1dnight | (~m1dnight@d8D861908.access.telenet.be) m1dnight |
| 2025-02-09 01:20:09 +0100 | mulk | (~mulk@pd95141d7.dip0.t-ipconnect.de) mulk |
| 2025-02-09 01:20:15 +0100 | otbergsten | (~otbergste@user/otbergsten) () |
| 2025-02-09 01:20:20 +0100 | Maxdamantus | (~Maxdamant@user/maxdamantus) Maxdamantus |
| 2025-02-09 01:20:33 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) (Ping timeout: 268 seconds) |
| 2025-02-09 01:21:15 +0100 | jathan | (~jathan@2607:1a00:0:19::2:1dc) jathan |
| 2025-02-09 01:25:14 +0100 | TMA | (tma@twin.jikos.cz) TMA |
| 2025-02-09 01:36:05 +0100 | zero | zwro |
| 2025-02-09 01:37:29 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) L29Ah |
| 2025-02-09 01:40:00 +0100 | alx741 | (~alx741@186.33.188.229) |