Newest at the top
| 2025-04-01 18:42:59 +0200 | kawzeg | (kawzeg@2a01:7e01::f03c:92ff:fee2:ec34) kawzeg |
| 2025-04-01 18:38:58 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
| 2025-04-01 18:35:05 +0200 | kawzeg | (kawzeg@2a01:7e01::f03c:92ff:fee2:ec34) (Quit: WeeChat 4.3.0) |
| 2025-04-01 18:34:45 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 276 seconds) |
| 2025-04-01 18:31:18 +0200 | danza | (~danza@user/danza) (Remote host closed the connection) |
| 2025-04-01 18:29:42 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
| 2025-04-01 18:29:18 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 246 seconds) |
| 2025-04-01 18:26:55 +0200 | aman | (~aman@user/aman) aman |
| 2025-04-01 18:24:53 +0200 | aman | (~aman@user/aman) (Ping timeout: 252 seconds) |
| 2025-04-01 18:20:33 +0200 | machinedgod | (~machinedg@d108-173-18-100.abhsia.telus.net) (Ping timeout: 248 seconds) |
| 2025-04-01 18:19:59 +0200 | merijn | (~merijn@77.242.116.146) (Ping timeout: 244 seconds) |
| 2025-04-01 18:15:32 +0200 | danza | (~danza@user/danza) danza |
| 2025-04-01 18:14:48 +0200 | ChanServ | +v haskellbridge |
| 2025-04-01 18:14:48 +0200 | haskellbridge | (~hackager@syn-024-093-192-219.res.spectrum.com) hackager |
| 2025-04-01 18:12:02 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
| 2025-04-01 18:11:51 +0200 | haskellbridge | (~hackager@syn-024-093-192-219.res.spectrum.com) (Remote host closed the connection) |
| 2025-04-01 18:10:41 +0200 | tomsmeding | is afk for a while |
| 2025-04-01 18:09:52 +0200 | <hellwolf> | right. i didn't realize it was closed and fixed. |
| 2025-04-01 18:09:36 +0200 | <tomsmeding> | you can indeed reply to the same issue; it's likely that you'll subsequently be instructed to create a new issue instead |
| 2025-04-01 18:09:00 +0200 | <hellwolf> | 9.10 |
| 2025-04-01 18:08:56 +0200 | <tomsmeding> | the fix for that PR is in 9.6; what GHC version are you using? |
| 2025-04-01 18:08:44 +0200 | <hellwolf> | I see, indeed. I might as well report one more sample to the same issue. |
| 2025-04-01 18:08:04 +0200 | <tomsmeding> | this actually sounds extemely related to https://gitlab.haskell.org/ghc/ghc/-/issues/22057 |
| 2025-04-01 18:07:17 +0200 | <hellwolf> | mxs_ & mxs_' |
| 2025-04-01 18:07:08 +0200 | <hellwolf> | https://paste.tomsmeding.com/wRfhejVB |
| 2025-04-01 18:06:48 +0200 | tomsmeding | suspects mx1_ |
| 2025-04-01 18:06:36 +0200 | <hellwolf> | let me find the error message, one sec |
| 2025-04-01 18:06:19 +0200 | <tomsmeding> | which variable do you get a warning about? |
| 2025-04-01 18:05:57 +0200 | <hellwolf> | here: https://paste.tomsmeding.com/JU7QBp5w |
| 2025-04-01 18:05:53 +0200 | <tomsmeding> | in general, if there's an issue in GHC, do report it; that's what the issue tracker is for |
| 2025-04-01 18:05:25 +0200 | <tomsmeding> | what is the case? Is it reasonable for GHC to detect it? |
| 2025-04-01 18:05:22 +0200 | <int-e> | the other versions do exist :) |
| 2025-04-01 18:04:55 +0200 | <hellwolf> | Considering the number of GHC issues, I don't think I should report and create one more issue there, for now. |
| 2025-04-01 18:04:55 +0200 | <hellwolf> | I had a minor bug, I used bang pattern in a TH quote, and GHC complaining that I have unused variable, but I clearly used it. |
| 2025-04-01 18:04:30 +0200 | <int-e> | good catch, thanks |
| 2025-04-01 18:04:22 +0200 | <tomsmeding> | ah |
| 2025-04-01 18:04:19 +0200 | <int-e> | so it fell back on 9.6.6 |
| 2025-04-01 18:04:16 +0200 | <tomsmeding> | what did it do :p |
| 2025-04-01 18:04:09 +0200 | <int-e> | I don't actually have 9.12.2 built, /opt/ghc-9.12.2 is empty |
| 2025-04-01 18:03:36 +0200 | <int-e> | oh that's my bad |
| 2025-04-01 18:03:15 +0200 | <tomsmeding> | I get a BangP both with 9.12.1 and 9.12.2 |
| 2025-04-01 18:02:58 +0200 | <int-e> | evidently? |
| 2025-04-01 18:02:21 +0200 | <tomsmeding> | it broke again in 9.12? |
| 2025-04-01 18:02:20 +0200 | <int-e> | So this was broken for a fairly long time. |
| 2025-04-01 18:02:12 +0200 | <tomsmeding> | _wat_ |
| 2025-04-01 18:01:59 +0200 | <tomsmeding> | oh wow |
| 2025-04-01 18:01:42 +0200 | <int-e> | tomsmeding: I was doing this experiment: https://paste.tomsmeding.com/Vbpiah8r |
| 2025-04-01 18:00:30 +0200 | <tomsmeding> | int-e: the thing about parentheses being relevant was just a brainfart; I think I completely misremembered this: https://gitlab.haskell.org/ghc/ghc/-/issues/22057 |
| 2025-04-01 18:00:18 +0200 | <hellwolf> | https://www.reddit.com/r/haskell/comments/kmk6q/the_best_ghc_bug_ever/ |
| 2025-04-01 17:59:34 +0200 | <hellwolf> | I remember SPJ said once that GHC deleted files at some point. Talking about better type system for managing side effects. |